Change additionalProperties default #612
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.
Resolves #607. A recent change (#585) allowed for the automatic addition of additional properties, so
& { [key: string]: any }
was added to all schema objects. The intent was to better reflect OpenAPI’s specification, and there is precedent for that. However, based on feedback, and previous expectations this library set, it was a little too disruptive.And so, this PR reverts that behavior, turning this off by default
, but adding a new
--additional-properties` flag to enable this behavior (outlined in the README). This is a good compromise of allowing that behavior, but requiring it to be opt-in (which is also probably better to be stricter by default).