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
I came across the following validation error for an empty string value after updating a field's format from email to idn-email:
"JSON is valid against more than one schema from 'oneOf'. Valid schema indexes: 0, 1."
Schema: { "properties": { "email": { "oneOf": [{ "format": "idn-email" }, { "const": "" } ] } }, "required": ["email"] }
{ "properties": { "email": { "oneOf": [{ "format": "idn-email" }, { "const": "" } ] } }, "required": ["email"] }
Test input: { "email": "" }
{ "email": "" }
...which means that "format": "idn-email" is accepting an empty string as an email address
"format": "idn-email"
The text was updated successfully, but these errors were encountered:
On further checking, it appears as if "format": "idn-email" accepts any string, including empty string, on https://www.jsonschemavalidator.net/
Sorry, something went wrong.
Unfortunately the idn-email format isn't supported.
idn-email
No branches or pull requests
I came across the following validation error for an empty string value after updating a field's format from email to idn-email:
"JSON is valid against more than one schema from 'oneOf'. Valid schema indexes: 0, 1."
Schema:
{ "properties": { "email": { "oneOf": [{ "format": "idn-email" }, { "const": "" } ] } }, "required": ["email"] }
Test input:
{ "email": "" }
...which means that
"format": "idn-email"
is accepting an empty string as an email addressThe text was updated successfully, but these errors were encountered: