-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose .onclose to the user connection. #5
base: master
Are you sure you want to change the base?
Conversation
Some esdoc improvements Logging that doesn't enforce string concatenation.
Ref T89 |
this.onMessage = null | ||
this.onClose = null | ||
this.onError = null | ||
this.onOpen = noop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if only WebSocket had a big o
this.onEnd = noop | ||
this.onMessage = noop | ||
this.onClose = noop | ||
this.onError = noop | ||
} | ||
|
||
connect(onMessage, onEnd, onOpen, connectionOptions) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is a part of me that really wants onOpen, onEnd
... but I can think of no justification, at all.
Looks good to me 👍 |
Some esdoc improvements
Logging that doesn't enforce string concatenation.
Resolves T89