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
We have a JSON schema that defines a string property with format uri-reference. This value for the string passes the validation:
uri-reference
\\this\\is\\a\\windows\\network\\path\\file.txt
According to RFC 3986 I believe it should not pass. Other validators do not allow this value under the same JSON schema we defined.
/^(([^:/?#]+?):)?(\/\/([^/?#]*))?([^?#]*)(\?([^#]*))?(#(.*))?/
ajv
/^(?:(?:[a-z][a-z0-9+\-.]*:)?\/?\/)?(?:[^\\\s#][^\s#]*)?(?:#[^\\\s]*)?$/i
The results are different, and it seems to me that in this case ajv does better.
Should this be considered a bug?
Thank you
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We have a JSON schema that defines a string property with format
uri-reference
. This value for the string passes the validation:According to RFC 3986 I believe it should not pass. Other validators do not allow this value under the same JSON schema we defined.
/^(([^:/?#]+?):)?(\/\/([^/?#]*))?([^?#]*)(\?([^#]*))?(#(.*))?/
ajv
validator instead does it like this:/^(?:(?:[a-z][a-z0-9+\-.]*:)?\/?\/)?(?:[^\\\s#][^\s#]*)?(?:#[^\\\s]*)?$/i
The results are different, and it seems to me that in this case
ajv
does better.Should this be considered a bug?
Thank you
The text was updated successfully, but these errors were encountered: