Repository navigation
Conversation
async effects without arguments are now deprecated
Contributor
|
A lot of misspellings of |
Collaborator
Author
|
I'm leaning towards deprecating async effects at the moment. I don't think it's possible to defined async effects with a single function. Rather it would probably need to be more like: effect = use_async_effect()
@effect.setup
async def my_effect_setup(): ...
@effect.teardown
async def my_effect_teardown(task): ...This seems like a different enough interface that we might want to supply it in a separate package (at least initially). |
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.
async effects without arguments are now deprecated
Checklist
Please update this checklist as you complete each item:
changelog.rsthas been updated with any significant changes.