Skip to content
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

Resource configuration, when adding a resource, all properties must have get and set #3

Open
brainwipe opened this issue Jun 8, 2016 · 0 comments

Comments

@brainwipe
Copy link
Owner

It must be possible to build a resource that has get properties, which you cannot set (such as calculated properties). If the client tries to change the "get only" properties then the system should use meta information to indicate that they are read only so that the client isn't under the illusion that they can be changed.

This solution isn't covered directly by the jsonapi specification, so I have started a conversation with the community.
http://discuss.jsonapi.org/t/post-patch-read-only-attibutes/522

@brainwipe brainwipe added this to the 1.0.6 milestone Sep 5, 2016
@brainwipe brainwipe modified the milestones: 1.0.6, 1.0.7 Oct 4, 2016
@brainwipe brainwipe removed this from the 1.0.7 milestone Feb 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant