Added async support to jwt_required view decorator #436
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
Owner
|
Awesome, thanks for the PR! I'll get a new version with this released shortly 👍 |
j178
reviewed
Jul 6, 2021
Contributor
Author
|
Thanks @j178, should have thought of that! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Now that Flask 2, which added Async/Await support, has been released extensions that provide decorators need to be updated in order to be used with Async/Await routes as per the documentation here
I've add the
flask.Flask.ensure_sync()method to the@jwt_requireddecorator so that it now can be used on Async/Await routes. If this is not added, a coroutine will be returned which in turn will cause Flask to return aTypeError.