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.
Important
Merging this pull request will create this release
Breaking Changes
Change some union variant names
When creating a union with
oneOf
,anyOf
, or a list oftype
, the name of each variant used to betype_{index}
where the index is based on the order of the types in the union.
This made some modules difficult to understand, what is a
my_type_type_0
after all?It also meant that reordering union members, while not a breaking change to the API, would be a breaking change
for generated clients.
Now, if an individual variant has a
title
attribute, thattitle
will be used in the name instead.This is only an enhancement for documents which use
title
in union variants, and only a breaking change forinline models (not
#/components/schemas
which should already have used more descriptive names).Thanks @wallagib for PR #962!