chore: pass SinkReplyBuilder and Transaction explicitly. Part1 #3946
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.
For some of our commands we need to inject another transaction and another SinkReplyBuilder. This results into error-prone injections of temporary objects into ConnectionContext. Most commands just need Transaction and SinkReplyBuilder, so lets pass them explicitly. The final goal will be to remove Transaction and reply_builder fields from ConnectionContext.