This repository has been archived by the owner on Nov 28, 2022. It is now read-only.
fix: missing operation schema exceptions #1180
Merged
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.
🧰 What's being changed?
oas
dependency to fix a bug where if a supplied path+method combination didn't exist in an OAS it was being searched for in though we'd still return an instance of theOperation
class, we'd return it with anundefined
schema
property. This error would then cascase and throw failures on any accessor of that class. Check out fix: operation being set to undefined if not found oas#371 for tests.🧬 Testing
Check out the attached
manual-api-missingInOas.json
example definition.Against
next
, this is what it currently looks like:And with this fix: