Define the multipleOfPrecision option for ajv to handle javascript number precision #1997
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Prism had trouble with the OAI multipleOf number constraint because the default ajv validation does not behave properly with non integer multipliers cf. https://github.com/ajv-validator/ajv/blob/master/lib/vocabularies/validation/multipleOf.ts
Eg: -4.02 multipleOf 0.01 was rejected because JS says
-4.02 / 0.01 = -401.99999999999994
This PR adds the AJV option to handle an error margin (1/1000th at the moment)
Checklist
Context
ajv-validator/ajv#84
ajv-validator/ajv#652