-
-
Notifications
You must be signed in to change notification settings - Fork 750
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
Should socket calls require a callback? #96
Comments
At the moment they do although the parameters object is optional. It shouldn't be hard to make the callback optional as well. You won't be able to handle any errors though (at the least I usually add an error handler callback). |
This is fixed in #107 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue with a link to this issue for related bugs. |
This feels like a bug to me. I've been trying to do a one-off update to the server like this:
Which results in a server crash on this error:
If I put the callback in place like this:
It works as expected. That doesn't seem right to me. Do socket calls always require the callback in place?
The text was updated successfully, but these errors were encountered: