-
Notifications
You must be signed in to change notification settings - Fork 58
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
Move Socket Outside #110
Comments
Your point seems realistic. @nishant23122000 this will help us in extending the socket in the future @kothariji |
@Vishv07 Yes |
Hi @nishant23122000 , First of all, thank you so much for taking out the time to work on this issue. Definitely 🙌, Please go forward to work on this issue. I am assigning this Issue to you 👍 And last but not least, |
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I think we should move all socket.io code outside of index.js in the backend because there is a bunch of socket.io events happening in index.js.
To Reproduce
Expected result
We can create an object of the socket in the socket.js file which we store in Utils folder So I think it's easy to understand index.js code and also code will be refactored in proper structure
Actual result
Screenshots
Are you willing to contribute to this issue? Yes
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: