Skip to content

Release 0.24.0 #1210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 3, 2025
Merged

Release 0.24.0 #1210

merged 1 commit into from
Mar 3, 2025

Conversation

knope-bot[bot]
Copy link
Contributor

@knope-bot knope-bot bot commented Mar 3, 2025

Important

Merging this pull request will create this release

Breaking Changes

Support $ref in responses

Previously, using a $ref to define a response was ignored, the code to call the endpoint was still generated, but
the response would not be parsed. Now, responses defined with $ref will be used to generate the response model, which
will parse the response at runtime.

If a $ref is incorrect or uses a feature that is not supported by the generator, these endpoints will start failing to
generate.

Features

Make config available in custom templates

The configuration options object is now exposed as a variable called config in Jinja2 templates.

Add docstrings_on_attributes config setting

Setting this option to true changes the docstring behavior in model classes: for any attribute that have a non-empty description, instead of describing the attribute as part of the class's docstring, the description will appear in an individual docstring for that attribute.

@dbanty dbanty enabled auto-merge March 3, 2025 01:25
@dbanty dbanty added this pull request to the merge queue Mar 3, 2025
Merged via the queue into main with commit d46544c Mar 3, 2025
21 checks passed
@dbanty dbanty deleted the knope/release branch March 3, 2025 01:32
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

## Breaking Changes

### Support `$ref` in responses

Previously, using a `$ref` to define a response was ignored, the code to
call the endpoint was still generated, but
the response would not be parsed. Now, responses defined with `$ref`
will be used to generate the response model, which
will parse the response at runtime.

If a `$ref` is incorrect or uses a feature that is not supported by the
generator, these endpoints will start failing to
generate.

## Features

### Make `config` available in custom templates

The configuration options object is now exposed as a variable called
`config` in Jinja2 templates.

### Add `docstrings_on_attributes` config setting

Setting this option to `true` changes the docstring behavior in model
classes: for any attribute that have a non-empty `description`, instead
of describing the attribute as part of the class's docstring, the
description will appear in an individual docstring for that attribute.

Co-authored-by: knope-bot[bot] <152252888+knope-bot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant