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
{{ message }}
This repository has been archived by the owner on Sep 28, 2021. It is now read-only.
function onAuthorizeSuccess(data, accept){
console.log('successful connection to socket.io');
// The accept-callback still allows us to decide whether to
// accept the connection or not.
accept(null, true);
// OR
// If you use [email protected] the callback looks different
accept();
}
It's unclear whether or not you should use accept(); or accept(null, true); for socket.io versions less than or greater than 1.0. The instructions only specify to use accept(); for any 1.X version, however it is unclear if accept(null, true); should be used for versions before or after 1.0. This is problematic, since there is currently a socket.io v4.X out.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This function is unclear:
It's unclear whether or not you should use
accept();
oraccept(null, true);
for socket.io versions less than or greater than 1.0. The instructions only specify to useaccept();
for any 1.X version, however it is unclear ifaccept(null, true);
should be used for versions before or after 1.0. This is problematic, since there is currently a socket.io v4.X out.The text was updated successfully, but these errors were encountered: