Add ability to revoke a socket ignoring if it is already closed #284
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.
In cases where there is an
onUnsubscribe
handler registered it is possible thatrevoke
can be called on a socket that has since been closed. This results in an error being thrown.To prevent having to try/catch and explicitly test for
nes
's internalSocket not open
error this new flagthrowIfClosed
allows the user to signal their intent to "fire and forget".Because
revoke
is async internally it is not possible to catch this with certainty prior to making therevoke
call.The added tests demonstrate the issue we are seeing in production.