[FIX] Allow default namespace to still be used #269
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.
Like others, I discovered that I wasn't able to use the default namespace for socket.io on the client side of the house. I tried to see if #254 would work, but something didn't seem quite right, so I took a stab at the code myself and I was able to get the desired behavior.
Default namespace
Here are some important snippets for using Vue-Socket.io with a default namespace:
src/main.js
src/components/HelloWorld.vue
server.js
Explicit namespace
And here are similar key snippets for when using a socket namespace is desired:
src/main.js
src/components/HelloWorld.vue
server.js