You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BEST code can easily get messy with lots of quotation marks used for selectors, events, etc. It'd be fantastic to switch to camelized names for event keys as it will significantly reduce the amount of quotation marks needed in behaviors and events sections of code. Camel case is more consistent with idiomatic JavaScript as well.
The only places I see that absolutely need dasherized strings wrapped with quotation marks are selectors, and we cannot really do much about it. However the rest can be changed for better developer experience.
The text was updated successfully, but these errors were encountered:
This seems sensible to me. I don't think there was a very strong reason to adopt the dasherized convention - other than aesthetics and readability. (I personally think foo-bar-baz is prettier and easier to read than fooBarBaz.) However I think developer convenience and convention should outweigh this, so it might be worth changing our recommended conventions. Tentative 👍
BEST code can easily get messy with lots of quotation marks used for selectors, events, etc. It'd be fantastic to switch to camelized names for event keys as it will significantly reduce the amount of quotation marks needed in
behaviors
andevents
sections of code. Camel case is more consistent with idiomatic JavaScript as well.The only places I see that absolutely need dasherized strings wrapped with quotation marks are selectors, and we cannot really do much about it. However the rest can be changed for better developer experience.
The text was updated successfully, but these errors were encountered: