Restore and implement the JsMsg.next() API.
#178
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
The `JsMsg.next()` method has been reintroduced and fully implemented, replacing its previous stubbed and commented-out state. This method combines `ack()` and `pull()` functionality, allowing for experimental subscription processing. The migration guide was updated to reflect the restoration of this API. Signed-off-by: Alberto Ricart <[email protected]>
aricart
force-pushed
the
restore-js-next
branch
from
818b26d to
66458f7
Compare
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.
The
JsMsg.next()method has been reintroduced and fully implemented, replacing its previous stubbed and commented-out state. This method combinesack()andpull()functionality, allowing for experimental subscription processing. The migration guide was updated to reflect the restoration of this API.