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 "readOnly" #228

Open
omid opened this issue Jun 14, 2021 · 5 comments
Open

Support "readOnly" #228

omid opened this issue Jun 14, 2021 · 5 comments

Comments

@omid
Copy link

omid commented Jun 14, 2021

Hello,

Do we support "readOnly"?
If yes, I couldn't figure it out, could you please lead me to a way to handle it?
If no, then it's a feature request :)

@Stranger6667
Copy link
Owner

Hi! Do you mean Open API's readOnly?

@Stranger6667
Copy link
Owner

Please, disregard my last comment.
Those annotations are not supported.

@Stranger6667
Copy link
Owner

Stranger6667 commented Jun 14, 2021

What would be the expected behavior then? from the validation point of view

@omid
Copy link
Author

omid commented Jun 14, 2021

Just to reference for the futures, I meant this: https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.9.4

IMHO:

  1. The simplest expected behavior could be to return some errors.
  2. The more advanced is, to accept a default (or previous) list of values to pick from.

@omid
Copy link
Author

omid commented Jun 14, 2021

Yep, the second one can be not related to validation, it's more sanitization.
It's similar to replace the "default" values in the lack of field.

@omid omid changed the title Does it support "readOnly"? Support "readOnly" Jun 14, 2021
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

2 participants