Closed marcodarko closed 4 years ago
Please reduce the example to the minimal size when it is still failing and post the failing code sample to runkit.com - it’s not clear what is what in the provided code.
It does look like the schema above and the one that is passed to Ajv are different
Hi, thank you I created this but this works. https://runkit.com/marcodarko/avj-schema-validator-test. However I'm not using node so I can't get the same error I see on my inspector console.
I'm sorry I updated the schema on this issue and the runkit version should be accurate too, I included the whole thing by accident but updated it to the part that avj receives. is the CDN version not up to date maybe? idk
Try reproducing it in a single script in the browser without dependencies - same script that works in runkit should work in the browser. There is nothing browser specific, unless you have some old browser.
Looking at the error, the schema above and what is passed to Ajv is not the same - so the problem might be in your code.
I’m going to close this issue - re-submit as browser / compatibility if these suggestions won’t help.
Also please use schema under say 20 lines - most issue usually can be reproduced with this size.
Just FYI I was able to reproduce the same error here : https://runkit.com/marcodarko/avj-schema-validator-test
“Required” on line 551 has a duplicate item “identifier”.
On 28 Sep 2020, at 22:59, Marco Cano notifications@github.com wrote:
Just FYI I was able to reproduce the same error here : https://runkit.com/marcodarko/avj-schema-validator-test
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.
What version of Ajv are you using? Does the issue happen if you use the latest version?
Ajv options object
JSON Schema
Sample data
Your code
Validation result, data AFTER validation, error messages
What results did you expect? I don't see any duplicates on required or on the data being validated so I would expect it to validate
Are you going to resolve the issue? I've tried adding older meta schemas with addMetaSchema but with no luck. I need help