Add "receiveWSMessage" and "sendWSMessage" to EventType type definition #39
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
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.
See #38
Description of Changes
Added
"receiveWSMessage"and"sendWSMessage"to theEventTypetype definition.This PR assumes that these two event types (which are already being emitted) are intended to be part of the public API. My current use case is to capture the size of the incoming and outgoing WebSocket message data to track the transfer rate up/down.
(This is a code-only change. Tests still pass, and I didn't see any existing tests for this level of event emitting so I didn't add any. Please let me know if I missed something there!)
API
N/A.
Requires SpacetimeDB PRs
N/A.