Handle the invalidate OOB push message.#2717
Closed
Conversation
- would argue that existing push message handlers should be handled in this manner, with the registration function not allowing one to overwrite "built in" handlers.
Contributor
Author
|
this should probably be closed and #2735 used instead. |
|
This pull request is marked stale. It will be closed in 30 days if it is not updated. |
|
This pull request has been automatically closed due to inactivity. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Provides a register callback that if set will be called when the client receives a key invalidate message from the server.
Checklist
npm testpass with this change (including linting)?