We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is no universal email validation, and I suggest that the language be loosened around this, for example.
In many places, there have been choices to make things up to the implementation. Perhaps this is already / should be one?
The text was updated successfully, but these errors were encountered:
In OAS 3.1, JSON Schema draft 2019-09 will be used, and as noted in #2093, format validation is disabled by default. For exactly this reason.
format
@webron @MikeRalphson I think this can be closed in favor of #2093 which will cover it. Unless we want to do something separate in 3.0.3, I guess.
Sorry, something went wrong.
@handrews - agreed.
No branches or pull requests
There is no universal email validation, and I suggest that the language be loosened around this, for example.
In many places, there have been choices to make things up to the implementation. Perhaps this is already / should be one?
The text was updated successfully, but these errors were encountered: