Use message context as inbound context when available #708
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
This way middlewares are able to mutate the message context and have that get threaded through to our invoker Signed-off-by: Ben Moss <[email protected]>
benmoss
force-pushed
the
messagecontext
branch
from
e9d58b6
to
ab9dab1
Compare
|
the failure is something with nats and not related to this PR. LGTM |
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 way middlewares are able to mutate the message context and have that get threaded through to our invoker. Right now the context that the invoker will receive is the one passed into
StartReceiver, which isn't as helpful.