Don't generate extra models for allOf
, oneOf
, or anyOf
of one model
#350
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.
Currently, we have tons of places where we do something like
which causes an unnecessary model
AaSequenceCustomFields
to be generated, rather than directly referencing the existingCustomFields
model.The OpenAPI 3.1 spec is going to add support for direct sibling properties:
But since that may be a long ways away, we directly implement a workaround in this PR.
This workaround also applies for
oneOf
andanyOf
.