-
Notifications
You must be signed in to change notification settings - Fork 96
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
Any plans for supporting readonly
marker ?
#986
Comments
This will require splitting server and client structures (i.e. different structures for client request and server request in signatures), which we want to avoid. Probably we can reconsider this on some point, because there is another feature that can lead to this split. |
Got it. So for now the only option is to have that split directly in the api definition, is that right? |
And to be honest, Ithink you don't need to split the structure between client and server. It would rather require generating different structure for post put and different structure for get etc. |
Oh, you are right. |
Any updates on this @ernado ? |
@ernado It would be super helpful thing. |
Description
Accordint to the specs, properites marked with readonly should not be send as part of a request body
but I'm getting bad request.
Do you plan to add support for readonly in a near future ?
References
https://spec.openapis.org/oas/v3.0.3#fixed-fields-19
The text was updated successfully, but these errors were encountered: