feat: improve additional properties support#126
Merged
Conversation
correctly interpret `{}`, `true` and `{type: "object"}` as
records of `unknown`, following guidance on free-form objects
from https://swagger.io/docs/specification/data-models/data-types/#object
mnahkies
force-pushed
the
mn/125/additional-properties
branch
from
549742c to
f497255
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Should help with #125 and #44
additionalPropertiesadditionalPropertiesNamely:
is equivalent to:
and
Based on the guidance about free-form objects here https://swagger.io/docs/specification/data-models/data-types/#object