This repository has been archived by the owner on Oct 5, 2023. It is now read-only.
feat: stop running schema dereferencing when running validation #153
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.
🧰 Changes
So a fun fact: when running
.validate()
on a schema we first dereference it with.deref()
and then whenswagger-parser
runs.validate()
on it it also does its own dereferencing. Since all.validate()
should do is validate something, this work changes it to no longer dereference. Anywhere. Ever.I've also swapped our our usage of
@apidevtools/json-schema-ref-parser
for pure@apidevtools/swagger-parser
as the two libraries already depend on each other and expose the same APIs.🧬 QA & Testing
See the test changes I made.