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

Support writeOnly + required combination #149

Closed
cdimascio opened this issue Nov 27, 2019 · 6 comments · Fixed by #936, #944, #951 or #960 · May be fixed by i3-Market-V3-Public-Repository/SP3-SCGBSSW-CR-ConflictResolverService#20
Closed

Comments

@cdimascio
Copy link
Owner

Notes below copied from @Haruki-Mortis readonly issue
Documentation definition
writeOnly (The writeOnly functionality has not been checked yet)

Relevant only for Schema "properties" definitions. Declares the property as "write only". Therefore, it MAY be sent as part of a request but SHOULD NOT be sent as part of the response. If the property is marked as writeOnly being true and is in the required list, the required will take effect on the request only. A property MUST NOT be marked as both readOnly and writeOnly being true. Default value is false.

related issue: #145

@mamatela
Copy link

Any progress on this? It would be so awesome to have this feature. It stands between me being able to use the same schema for get and post operations vs having to create separate almost-duplicates.

@na2793
Copy link

na2793 commented Mar 3, 2021

I am also curious about this. I really need this feature.

pdhau added a commit to pdhau/express-openapi-validator that referenced this issue Sep 17, 2022
@Mike-J-W
Copy link

Mike-J-W commented Nov 6, 2023

Commenting to say this feature is still desired. And that a pull request exists for it, #756, if @cdimascio could review it.

@cdimascio
Copy link
Owner Author

available in v5.1.5. thanks @pdhau

@cdimascio
Copy link
Owner Author

@all-contributors add @pdhau for code and test

Copy link
Contributor

@cdimascio

I've put up a pull request to add @pdhau! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment