-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Data Type Format validation #139
Comments
Hi @baurchanu , Thanks for the suggestion. I'll look into it in 2021. For the moment, the configuration of By the way, if you have time to create a PR for this, I will take the time to review it and merge it if everything is ok. |
ok, i'll try to implement this and create a PR |
Hi @baurchanu , Did you start something for this? Just coming back from the holidays and wanted to know if you had something (no pressure! ). |
@JFCote hi, yes I've examined the project and working on this issue. Sorry for the delay. We have too long and discouraging new year holidays in Russia :) |
@baurchanu No problem, take your time! |
Sorry, I'm not planning to implement this feature anymore, 'cause I migrated my project to zally. |
@baurchanu Looks like a nice project! Thanks for letting me know. |
Is the format even validated? As far as I can see it is not validated at all. |
Hi, it might be an option to add validation of data type format.
Use case:
Date time format validation.
On my current project we use custom formats (not ISO / RFC). So I'd like to have something like this in configuration:
By default all standard OAS formats are allowed and all custom formats are forbidden.
Valid schema:
Not valid schema:
The text was updated successfully, but these errors were encountered: