-
Notifications
You must be signed in to change notification settings - Fork 96
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
Args are not optional when using a Callback. #131
Comments
Sure that's how multiple params work. I suppose I could look at the 2nd param type and make some determination on that. |
Usually in nodeJS/javascript you can do
or
or
And
It's not a problem just the docs are wrong as if I should pass |
I'd have to check my code and see what I'm using. I believe I'm primarily using callbacks so it would be a breaking change for me. Not a problem but it does reduce user choice/flexibility. |
Seems good to me! |
Description:
This does not work
This does work
I added some weird logging™ to OBSWebSocket.js
And observed that the callback function was attempted to be stringified and passed to OBS over the socket…
You cannot have a callback, and have the arguments be optional.
Versions Used (if applicable):
The text was updated successfully, but these errors were encountered: