allow internal kv watch consumer to use filtered consumer api #662
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
… supported by the server. This enables the client to be able to use the newer consumer APIs which can then be clamped down with permissions on filter [FIX] removed unused JSM reference in the Views implementation
jetstream/tests/kv_test.ts
Outdated
| const iter = await kv.watch({ key: "a.>" }); | ||
|
|
||
| const m = await sub.next(); | ||
| console.log(m?.subject); |
There was a problem hiding this comment.
@ramonberrutti thanks Ramon!!
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.
[FIX] changed KV ordered consumers created by watch, to set
nameif supported by the server. This enables the client to be able to use the newer consumer APIs which can then be clamped down with permissions on filter[FIX] removed unused JSM reference in the Views implementation