Teach Prism to stop polluting the console with AJV "unknown format" warnings #1889
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
In ajv-validator/ajv#466, the author of AJV makes it very clear that people should be aware of unknown formats.
However, according to the OpenAPI spec, format is is an open string-valued property, and can have any value.
Given some traffic, all those warnings tend to pollute the console output a lot and make it very hard to follow up with what's logged by Prism.
This change intercepts AJV calls to console.warn and when they relate to unknown formats, silence them.
Checklist
Screenshots
Given the following spec
openapi.yaml
stored at the root of the repo workdirFrom a term, run the following
From another term, run the following
Switch back to intial term and observe the generated log
Additional context
A similar issue has been opened ages ago against Spectral (stoplightio/spectral#396).
This PR
shamelessly stolesis greatly inspired by @chris-miaskowski 's fix from stoplightio/spectral#503