-
-
Notifications
You must be signed in to change notification settings - Fork 877
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
Handling of URL encoding changed/broke in 8.15 #2447
Comments
Encountering this same issue since last night and was wondering why my builds are failing. https://github.com/ajv-validator/ajv/releases/tag/v8.15.0 |
Reverting now. New version will be 8.16.0 and will set everything back to how it was in 8.14.0. Sorry for the disruption. |
Reverted in v8.16.0 I will close this but keep this as a reference when considering how best to deal with uri-js. |
Thanks for the quick fix, @jasoniangreen. |
I can confirm that 8.16.0 works fine for all my use cases. Thanks! |
I'm currently investigating this - just noting that if you do not preencode your $ref, it works correctly, and from the output, it seems like we double encode and not decode later or decode incorrectly |
What version of Ajv are you using? Does the issue happen if you use the latest version?
8.15 (latest version)
Ajv options object
JSON Schema
Sample data
Your code
Validation result, data AFTER validation, error messages
Compiler error:
What results did you expect?
Successful compilation of the schema. This worked in 8.14 and works in https://www.jsonschemavalidator.net/, but 8.15's change of URL library seems to have altered its behavior.
Are you going to resolve the issue?
I know that 8.15's URL parser changes are actively being worked on, but I can help if needed.
The text was updated successfully, but these errors were encountered: