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

Readonly attributes are a challenge in the client #50

Open
stomli opened this issue Jan 31, 2017 · 0 comments
Open

Readonly attributes are a challenge in the client #50

stomli opened this issue Jan 31, 2017 · 0 comments

Comments

@stomli
Copy link

stomli commented Jan 31, 2017

Is it possible for the client to "know" which attributes are readonly and to not submit these when "sync"ing?

I have a resource with a couple readonly attributes, on the server I modify the resource in beforecreate to fill these attributes. Works great at creation, however if I know get that resource and do any update to it, it fails as the client submits all the readonly attributes that came down with the resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant