-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confirm all response messages against spec #178
Comments
➤ Ivan Senic commented: PR #1 countDocuments command: #202 ( https://github.com/stargate/jsonapi/pull/202|smart-link ) |
ivansenic
pushed a commit
that referenced
this issue
Mar 1, 2023
6 tasks
ivansenic
pushed a commit
that referenced
this issue
Mar 1, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 1, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 2, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 2, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 2, 2023
➤ Ivan Senic commented: Futher PRs:
|
10 tasks
ivansenic
pushed a commit
that referenced
this issue
Mar 8, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 9, 2023
7 tasks
maheshrajamani
pushed a commit
that referenced
this issue
Mar 9, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 13, 2023
➤ Ivan Senic commented: Further PRs: |
ivansenic
pushed a commit
that referenced
this issue
Mar 13, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 15, 2023
8 tasks
ivansenic
pushed a commit
that referenced
this issue
Mar 15, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 16, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 16, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 16, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 16, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 20, 2023
ivansenic
pushed a commit
that referenced
this issue
Mar 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue #175 has updates to the API spec that locks in the response messages from a meeting today.
The API spec now has a general description of the request and response, and each command specifies the data is should return.
This is a catchall ticket to ensure those changes to the spec and the code are in sync. There may be some changes that have already happened like removing the updatedId's list from the status.
I think the spec changes are good based on the meeting today, and we can probably start implementing.
@maheshrajamani and @ivansenic this also includes the response data when there are errors. Still have changes for #160 in my git stash, but this describes what the response should be.
The text was updated successfully, but these errors were encountered: