You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion there are plenty of cases where one might want to send something through a websocket but not necessarily care about the callback. Currently, this requires the user to specify an empty callback handler.
@0x00002a what do you think about providing a default callback handler (an empty one) so a user might just do this:
Agreed, that would be better. There does need to be a way to report errors though, I don't like the idea of letting the user easily (potentially accidentially even) ignore them, which I guess is more #40.
In my opinion there are plenty of cases where one might want to send something through a websocket but not necessarily care about the callback. Currently, this requires the user to specify an empty callback handler.
@0x00002a what do you think about providing a default callback handler (an empty one) so a user might just do this:
instead of:
The text was updated successfully, but these errors were encountered: