Release 0.24.0 #1208
Closed
Release 0.24.0 #1208
Conversation
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
knope-bot
bot
force-pushed
the
knope/release
branch
from
9cc27f3 to
44b1fbc
Compare
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
Breaking Changes
Support
$refin responsesPreviously, using a
$refto define a response was ignored, the code to call the endpoint was still generated, butthe response would not be parsed. Now, responses defined with
$refwill be used to generate the response model, whichwill parse the response at runtime.
If a
$refis incorrect or uses a feature that is not supported by the generator, these endpoints will start failing togenerate.
Features
Make
configavailable in custom templatesThe configuration options object is now exposed as a variable called
configin Jinja2 templates.Add
docstrings_on_attributesconfig settingSetting this option to
truechanges the docstring behavior in model classes: for any attribute that have a non-emptydescription, instead of describing the attribute as part of the class's docstring, the description will appear in an individual docstring for that attribute.