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
We should document these two cases in https://github.com/venuu/jsonapi-authorization/blob/master/docs/relationship-authorization.md:
GET /source_record/:id/has-one-resource
GET /source_record/:id/has-many-resources
Look at the existing docs in that file as an example on how these specs should be written.
Originally posted by @valscion in #113 (comment)
It is not mentioned in the docs, only the create/update/delete behaviour of relationships is in the docs, but that is a different case. Oh wow, that seems like an oversight. I'll create an issue about this, as we will likely want to document this in https://github.com/venuu/jsonapi-authorization/blob/master/docs/relationship-authorization.md
It is not mentioned in the docs, only the create/update/delete behaviour of relationships is in the docs, but that is a different case.
Oh wow, that seems like an oversight. I'll create an issue about this, as we will likely want to document this in https://github.com/venuu/jsonapi-authorization/blob/master/docs/relationship-authorization.md
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We should document these two cases in https://github.com/venuu/jsonapi-authorization/blob/master/docs/relationship-authorization.md:
GET /source_record/:id/has-one-resource
GET /source_record/:id/has-many-resources
Look at the existing docs in that file as an example on how these specs should be written.
Originally posted by @valscion in #113 (comment)
The text was updated successfully, but these errors were encountered: