We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Relating to the upcoming sideposting pr to json-api json-api/json-api#1197
Has anyone put any thought into how this can be handled by jsonapi-resources?
jsonapi-resources
We have the operations pr #951 which would be good to make use of if possible, treating sideposted resources as separate operations.
Does that seem like the right way to go?
The text was updated successfully, but these errors were encountered:
JR will support the eventual outcome of json-api/json-api#1197. I'm in favor of the Local ID terminology.
Beyond sideposting I think there's still a need for operations. I hope local ids could be used to replace the JSON pointers in #951.
Sorry, something went wrong.
No branches or pull requests
Relating to the upcoming sideposting pr to json-api json-api/json-api#1197
Has anyone put any thought into how this can be handled by
jsonapi-resources
?We have the operations pr #951 which would be good to make use of if possible, treating sideposted resources as separate operations.
Does that seem like the right way to go?
The text was updated successfully, but these errors were encountered: