style

Style

A guide for programming in style.

Git

• Avoid including files in source control that are specific to your development machine or process.
• Delete local and remote feature branches after merging.
• Perform work in a feature branch.
• Prefix feature branch names with your initials.
• Rebase frequently to incorporate upstream changes.
• Use a pull request for code reviews.
• Write a good commit message.

Formatting

• Avoid inline comments.
• Break long lines after 80 characters.
• Delete trailing whitespace.
• Don't include spaces after (, [ or before ], ).
• 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.
• 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.
• Use 2 space indentation (no tabs).
• Use an empty line between methods.
• Use newlines around multi-line blocks.
• Use spaces around operators, after commas, after colons and semicolons, around { and before }.
• Use Unix-style line endings (\n).
• Use uppercase for SQL key words and lowercase for SQL identifiers.

Naming

• Avoid abbreviations.
• Avoid types in names (user_array).
• Name the enumeration parameter the singular of the collection.
• Name variables, methods, and classes to reveal intent.
• Treat acronyms as words in names (XmlHttpRequest not XMLHTTPRequest), even if the acronym is the entire name (class Html not class HTML).
• Name variables holding a factory with _factory (user_factory).
• Name variables created by a factory after the factory (user_factory creates user).

CSS

• Use Sass.

Sass

• Use the Scss syntax.
• Use dashes when naming mixins, extends, classes or IDs: span-columns not span_columns or spanColumns.
• Use descriptive names and write them in full-words: $visual-grid-color not $color or $vslgrd-clr.
• Use space between property and value: width: 20px not width:20px.
• Order properties within rule sets alphabetically.
• Leave a blank line between rule sets.

JavaScript

• Use CoffeeScript.

CoffeeScript

• Initialize arrays using [].
• Initialize empty objects and hashes using {}.
• Use CamelCase for classes, lowerCamelCase for variables and functions, SCREAMING_SNAKE_CASE for constants, _single_leading_underscore for private variables and functions.
• Prefer is to == or ===
• Prefer or and and to || and &&

Ruby

Sample

• Avoid conditional modifiers (lines that end with conditionals).
• Avoid organizational comments (# Validations).
• Avoid ternary operators (boolean ? true : false). Use multi-line if instead to emphasize code branches.
• Avoid explicit return statements.
• Prefer detect over find.
• Prefer inject over reduce.
• Prefer map over collect.
• Prefer select over find_all.
• Prefer single quotes for strings.
• Use _ for unused block parameters.
• Use %{} for single-line strings needing interpolation and double-quotes.
• Use && and || for Boolean expressions.
• Use {...} for single-line blocks. Use do..end for multi-line blocks.
• Use ? suffix for predicate methods.
• Use CamelCase for classes and modules, snake_case for variables and methods, SCREAMING_SNAKE_CASE for constants.
• Use def self.method, not def Class.method or class << self.
• Use def with parentheses when there are arguments.
• Use each, not for, for iteration.
• Use heredocs for multi-line strings.

ERb

Sample

• When wrapping long lines, keep the method name on the same line as the ERb. interpolation operator and keep each method argument on its own line.

Rails

• Avoid member and collection routes.
• Avoid the :except option in routes.
• Don't reference a model class directly from a view.
• Don't use protected controller methods.
• Don't use SQL or SQL fragments (where('inviter_id IS NOT NULL')) outside of models.
• Keep the db/schema.rb under version control.
• If there are default values, set them in migrations.
• Name initializers for their gem name.
• Order ActiveRecord associations alphabetically by attribute name.
• Order ActiveRecord validations alphabetically by attribute name.
• Order controller contents: filters, public methods, private methods.
• Order model contents: constants, macros, public methods, private methods.
• Order resourceful routes alphabetically by name.
• Put application-wide partials in the app/views/application directory.
• Use _path, not _url, for named routes everywhere except mailer views.
• Use def self.method, not the scope :method DSL.
• Use SQL, not ActiveRecord models, in migrations.
• Use the default render 'partial' syntax over render partial: 'partial'.
• Use the :only option to explicitly state exposed routes.

Background Jobs

• Define a PRIORITY constant at the top of delayed job classes.
• Define two public methods: self.enqueue and perform.
• Put delayed job classes in app/jobs.

Email

• Use one ActionMailer for the app. Name it Mailer.
• Use the user's name in the From header and email in the Reply-To when delivering email on behalf of the app's users.

Testing

Sample

• Avoid its, let, let!, specify, before, and subject.
• Avoid using instance variables in tests.
• Avoid scenario titles that add no information, such as "successfully."
• Avoid scenario titles that repeat the feature title.
• Avoid the private keyword in specs.
• Don't prefix it block descriptions with 'should'.
• Include the Features module in RSpec scenarios with :type => :feature set.
• Name outer describe blocks after the method under test. Use .method for class methods and #method for instance methods.
• Order ActiveRecord association tests alphabetically by attribute name.
• Order ActiveRecord validation tests alphabetically by attribute name.
• Order factories.rb contents: sequences, traits, factory definitions.
• Order factory attributes: implicit attributes, explicit attributes, child factory definitions. Each section's attributes are alphabetical.
• Order factory definitions alphabetically by factory name.
• Place helper methods for feature specs directly in a top-level Features module.
• Prefer eq to == in RSpec.
• Separate setup, exercise, verification, and teardown phases with newlines.
• Use an it example for each execution path through the method.
• Use one factories.rb file per project.
• Use stubs and spies (not mocks) in isolated tests.
• Use a single level of abstraction within scenarios.
• Use names like ROLE_ACTION_spec.rb, such as user_changes_password_spec.rb, for feature spec file names.
• Use only one feature block per feature spec file.
• Use scenario titles that describe the success and failure paths.
• Use spec/features to store feature specs.
• Use spec/support/features for support code related to feature specs.

Objective-C

Sample

• #import linked frameworks in the prefix header (ProjectName-Prefix.pch).
• Keep .xib files grouped with their associated view class.
• Order #import statements alphabetically.
• Order @class directives alphabetically.
• Order @property modifiers: memory management, atomicity, writability.
• Organize classes into models, views, controllers, categories, and services directories.
• Prefer @class to #import when referring to external classes in a public @interface.
• Prefer @property to declaring instance variables.
• Prefix class names with a 2-letter project acronym.
• Prefix string constants being used as keys with 'k'.
• Remove #import statements for Foundation and UIKit in new project templates.
• Separate methods by function using #pragma mark - <Section Name>
• Separate sections into subsections using #pragma mark <Subsection Name>
• Use @[arrayObject], @{@"key" : value}, @(YES or NO), and @5.0 literals.
• Use @interface ClassName () to declare private properties.
• Use lowerCamelCase for method names.
• Use NSAssert in methods that require the presence of certain arguments.
• Write methods using the happy path. Indent the exceptional cases. Keep the optimal case in the left-most column.

Python

• Follow PEP 8.