Add support for asynchronous workflows with ContextVar #18
+37
−46
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
…s str along with initial else condition that throws an error specifying what the database parameter should be of type. add comments and clean up
feat: add support for async operations
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.
This pull request introduces an update to the dynamic-db-router extension by replacing
threading.localwithContextVar. This change enhances the extension's ability to handle context better, specifically in asynchronous environments.Key Changes:
threading.localwithContextVarfor maintaining database routing context. This shift allows the router to maintain state across both synchronous threads and asynchronous tasks.Benefits:
We believe these changes will make the dynamic-db-router more versatile.