fix: magically resolving objects that are typod as arrays #132
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
domharrington
approved these changes
Mar 20, 2020
2 tasks
This was referenced Jun 4, 2021
This was referenced Sep 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since launching v6 of the Explorer, we've gotten a number of reports come through Sentry of OAS documents being used rendered that have
type: arraywhen they should betype: object. It's no fault of ours, but since we can see that they intended for it to betype: objectaspropertiesand notitemsis present on that schema, we can infer and shape the data into what they intended it to be and avoid any fatal rendering errors.Resolves README-6R in Sentry.