feat(#8): add Socket.IO support with socketioxide integration 😭 #19
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Phosphorus-M
force-pushed
the
socketio
branch
2 times, most recently
from
873c060 to
cc2dd0d
Compare
Phosphorus-M
force-pushed
the
socketio
branch
from
cc2dd0d to
c991aed
Compare
Phosphorus-M
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Surely there are parts that could be made smarter, but honestly I was already tired. Maybe I’ll iterate on it later to improve the WebSocket part a bit. Still, everything is isolated in its own module with its respective feature flag, so… yeah, that