-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Custom event naming convention #1571
Comments
this would be better suited for stack overflow. Internal events for socket.io are camel cased strings. I think you best use whatever style suits you best. I think it is better to use dashes and small case letters, because frankly in javascript everything is camel cased and it is always nice to be able to differentiate based on a formatting. |
I have seen examples with 1) lower case and underscore and 2) camelcase, Altso,should I use present tense or past? |
Here are a few internal event name examples:
Like @capaj mentioned, it's really up to you how you want to name them. A pretty common way is to not do camel case, but add whitespace, such as |
What event naming conventions does socket.io project follow? I would like to reuse it for my custom events as well, in order to make the application.
The text was updated successfully, but these errors were encountered: