-
Notifications
You must be signed in to change notification settings - Fork 301
JSON API 1.1: cursor-pagination profile #548
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
Comments
As far as I understand is this is rather an example and not an actual profile as JSON API is still pagination strategy agonistc. I think in case of profile the only relevant issue for DJA at this point is #558 |
See https://github.com/json-api/json-api/blob/gh-pages/_profiles/ethanresnick/cursor-pagination/index.md which looks like cursor pagination is a registered profile. Profiles adds a new profile media type parameter and query parameter, so at a minimum QueryParameterValidation would need to add this as well? |
OK let's leave this issue open then. I seems it duplicates #320 and I guess we should close one of those two? As this is additional profile as I understand it is it not necessarily needed to fully support JSON API 1.1 but rather an addition which an implementation might implement. I have split up media and query parameter support #560 which will be the base once the first additional profile is implemented. The profile change in JSON API 1.1 seems to be a fairly big change which we certainly have to have a closer look what it really involves before we implement. |
Closing as explained at #547 (comment) Once JSON API spec is moving forward we need to double check which issue need to be reopened. |
See #547. Analyze new cursor-pagination profile
The text was updated successfully, but these errors were encountered: