js: use custom inbox prefix in async reply #1190
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: Guillaume Delbergue <guillaume.delbergue@hiventive.com>
wallyqs
reviewed
Jan 17, 2023
There was a problem hiding this comment.
LGTM, could you cherry pick or include the test code from this commit into your branch? wallyqs@31c48cd
Signed-off-by: Waldemar Quevedo <wally@nats.io>
Sure, I added your commit. Thanks |
wallyqs
approved these changes
Jan 17, 2023
Merged
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 PR uses Custom Inbox prefix in JS async reply. It should fix #1189
Signed-off-by: Guillaume Delbergue guillaume.delbergue@hiventive.com