Skip to content

Some additional notes on naming conventions #165

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

unkillbob
Copy link
Contributor

In the process of forking your amazing style guide and porting across some of the differences in our old internal style guide, we found some additional notes on naming conventions we thought might be worth sharing.

Includes recommendations on naming abbreviations, acronyms, constants and class methods.

… on abbreviations, acronyms, constants and class methods.
@ghost
Copy link

ghost commented Aug 10, 2015

Note that constant naming is also discussed in #255

@@ -995,7 +995,7 @@

## Naming Conventions

- Avoid single letter names. Be descriptive with your naming.
- Avoid single letter names. Be descriptive with your naming. Names representing types should be nouns. Names representing methods should be verbs or verb phrases.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JS doesn't really have "methods" - could this be functions instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants