Merged
Conversation
63f3766 to
8864a5f
Compare
66c3036 to
cd3e70b
Compare
dbanty
approved these changes
Oct 20, 2024
micha91
pushed a commit
to micha91/openapi-python-client
that referenced
this pull request
May 13, 2025
> [!IMPORTANT] > Merging this pull request will create this release ## Features - update Ruff to >=0.2,<0.8 (openapi-generators#1137) - Add UUID string format. Thanks @estyrke! (openapi-generators#1140) - Support OpenAPI 3.1 prefixItems property for arrays. Thanks @estyrke! (openapi-generators#1141) ### Add `literal_enums` config setting Instead of the default `Enum` classes for enums, you can now generate `Literal` sets wherever `enum` appears in the OpenAPI spec by setting `literal_enums: true` in your config file. ```yaml literal_enums: true ``` Thanks to @emosenkis for PR openapi-generators#1114 closes openapi-generators#587, openapi-generators#725, openapi-generators#1076, and probably many more. Thanks also to @eli-bl, @expobrain, @theorm, @chrisguillory, and anyone else who helped getting to this design! ## Fixes - Typo in docstring (openapi-generators#1128) ### Use literal value instead of `HTTPStatus` enum when checking response statuses Python 3.13 renamed some of the `HTTPStatus` enum members, which means clients generated with Python 3.13 may not work with older versions of Python. This change stops using the `HTTPStatus` enum directly when checking response statuses. Statuses will still be checked for validity at generation time, and transformed into `HTTPStatus` _after_ being checked at runtime. This may cause some linters to complain. Co-authored-by: knope-bot[bot] <152252888+knope-bot[bot]@users.noreply.github.com>
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
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
Features
Add
literal_enumsconfig settingInstead of the default
Enumclasses for enums, you can now generateLiteralsets whereverenumappears in the OpenAPI spec by settingliteral_enums: truein your config file.Thanks to @emosenkis for PR #1114 closes #587, #725, #1076, and probably many more.
Thanks also to @eli-bl, @expobrain, @theorm, @chrisguillory, and anyone else who helped getting to this design!
Fixes
Use literal value instead of
HTTPStatusenum when checking response statusesPython 3.13 renamed some of the
HTTPStatusenum members, which means clients generated with Python 3.13 may not workwith older versions of Python. This change stops using the
HTTPStatusenum directly when checking response statuses.Statuses will still be checked for validity at generation time, and transformed into
HTTPStatusafter being checkedat runtime.
This may cause some linters to complain.