We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/mfrachet/use-socketio/blob/73601fec48506de4eada21f6f3bdb1aef92122cf/src/useSocket.js#L11
Could be ? (check https://github.com/parweb/use-socketio/pulls?q=is%3Apr+is%3Aclosed) return [value, (message) => socket.emit(eventKey, message), socket];
return [value, (message) => socket.emit(eventKey, message), socket];
The text was updated successfully, but these errors were encountered:
It absolutely could 😊 You can pr on this if you'd like to 😄
Sorry, something went wrong.
Since the v1.0.0 has been published, it's not possible to rely on a callback to avoid unecessary state modifications
No branches or pull requests
https://github.com/mfrachet/use-socketio/blob/73601fec48506de4eada21f6f3bdb1aef92122cf/src/useSocket.js#L11
Could be ? (check https://github.com/parweb/use-socketio/pulls?q=is%3Apr+is%3Aclosed)
return [value, (message) => socket.emit(eventKey, message), socket];
The text was updated successfully, but these errors were encountered: