Expose nats.Context option for nats.KeyWatcher #904
Merged
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
Signed-off-by: Matthew DeVenny <[email protected]>
Signed-off-by: Matthew DeVenny <[email protected]>
wallyqs
reviewed
Feb 10, 2022
Signed-off-by: Matthew DeVenny <[email protected]>
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.
Signed-off-by: Matthew DeVenny [email protected]
Currently if you wish to extend the
nats.KeyValueinterface, when implementingWatchyou have no means to get at thenats.Contextoption if it has been set on thenats.KeyWatcher. This PR proposes a method to the nats.KeyWatcher to access that context.