-
Notifications
You must be signed in to change notification settings - Fork 9
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
Global Variable Naming #13
Comments
I think I like number 1, but there's something clear about |
I vote for style 1 too! caps works well for scalar values i think but then when there are global objects then THAT_GLOBAL_FORMATTER(toString:date) would seem funny. |
Should we say use the all caps for scalar values (i.e. |
I think if we're using all caps, that should also apply to strings in which case, what variable would not use all caps? @brightredchilli I think in terms of objects, it's probably best not to have them globally accessible and instead wrap them in an accessor the way we often do |
1️⃣ |
Should they be capitalized, like:
The text was updated successfully, but these errors were encountered: