-
Notifications
You must be signed in to change notification settings - Fork 16
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 writeOnly support #16
Comments
|
@raveclassic, what do you think about this? that will allow us not to break existing types (that don't have readonly or writeonly fields). at the same time we can avoid checking if type has readonly or writeonly fields.
|
removing from milestone as it might require a lot of work when there's a simple and maintainable workaround available - just to split models by hand and use different references across the spec |
No description provided.
The text was updated successfully, but these errors were encountered: