A guide for programming in style.
Use Hound to automatically review your GitHub pull requests for style guide violations.
In addition to the general guidelines below, we also have the following more detailed, language/framework-specific style guides:
- Avoid inline comments.
- Break long lines after 80 characters.
- Delete trailing whitespace.
- Don't include spaces after
- Don't misspell.
- Don't vertically align tokens on consecutive lines.
- If you break up an argument list, keep the arguments on their own lines and closing parenthesis on its own line. Example 1 Example 2
- If you break up a hash, keep the elements on their own lines and closing curly brace on its own line.
- Indent continued lines two spaces.
- Indent private methods equal to public methods.
- If you break up a chain of method invocations, keep each method invocation on
its own line. Place the
.at the end of each line, except the last. Example.
- Use 2 space indentation (no tabs).
- Use an empty line between methods.
- Use empty lines around multi-line blocks.
- Use spaces around operators, except for unary operators, such as
- Use spaces after commas, after colons and semicolons, around
- Use Unix-style line endings (
- Use uppercase for SQL key words and lowercase for SQL identifiers.
- Avoid abbreviations.
- Avoid object types in names (
- Prefer naming classes after domain concepts rather than patterns they
- Name the enumeration parameter the singular of the collection.
- Name variables created by a factory after the factory (
- Name variables, methods, and classes to reveal intent.
- Treat acronyms as words in names (
XMLHTTPRequest), even if the acronym is the entire name (
- Suffix variables holding a factory with
- Order methods so that caller methods are earlier in the file than the methods they call.
- Order methods so that methods are as close as possible to other methods they call.