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.
This PR contains the following updates:
==2.14.2
->==3.0.0
By merging this PR, the issue #362 will be automatically resolved and closed:
Release Notes
spec-first/connexion (connexion)
v3.0.0
Compare Source
Connexion 3.0: API-first for all
We are excited to announce the release of Connexion 3.0! 🎉
Connexion 3 fundamentally changes how Connexion is designed and implemented, and how it
fits into the wider Python API ecosystem. We adopted the ASGI interface, which makes Connexion both
modular and well-integrated with most modern Python API tooling.
It brings some major changes compared to 2.X:
App
and newAsyncApp
allow you to use Connexion as a stand-alone frameworkApp
interface was extended so you no longer have to care about the framework usedunderneath
with its spec-based functionality
with multiple content types and making it easy to add validation for additional content types
add support for additional security schemes.
our documentation
_For further details, check:
Full changelog
add_middleware
interface by @RobbeSneyders in https://github.com/spec-first/connexion/pull/1683New Contributors
Full Changelog: spec-first/connexion@2.13.0...3.0.0