feat: add an option to the pipeline feature to be able to select either throwing an error or returning errors as is #343
Conversation
This file contains 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
Member
supercaracal
commented
Apr 10, 2024
•
supercaracal
commented
- About error handling of pipelining redis-client#28
- Raise errors from #pipelined instead of returning them #297
- add flag to disable raising exceptions with pipelined redis-client#187
supercaracal
changed the title
supercaracal
changed the title
supercaracal
changed the title
supercaracal
changed the title
|
@supercaracal Let us know when you're ready to merge this PR Cheers! |
|
Thank you! |
supercaracal
deleted the
add-an-option-to-pipeline-for-throwing-an-exception-or-not
branch
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.