Skip to content

Latest commit

 

History

History
24 lines (16 loc) · 1.43 KB

coding-styles.md

File metadata and controls

24 lines (16 loc) · 1.43 KB
Raw
title position
Coding Styles
5

Coding Styles

GIT conventions

In general terms, we agree with almost everything said in this blog post about GIT conventions and so should you. We only add/differ the following:

Commits should try to be as simple (atomic) as possible, but not simpler. Meaning you should always be able to revert specific fixes, edits, updates, adds, and removes with git revert

Javascript

We use eslint to check our code for the coding styles specified in the .eslintrc file in the root of the app, you can configure your text editor to give you hints when you don't follow the styles.

Stylesheets

  • See .stylintrc file. More info: https://rosspatton.github.io/stylint1-0/
  • For module specific styles, comply with #unique-template-top-node-selector .my-generic-css-update { ... }
  • .classes and #ids should only be used to reference from CSS files. If you want to use some element from JS use data-* to always be sure where the element is referenced from.
  • For multiple, comma-separated selectors, place each selector on its own line.
  • Attribute selectors, like input[type="text"] should always wrap the attribute's value in double quotes, for consistency and safety (see this blog post on unquoted attribute values that can lead to XSS attacks).