-
Notifications
You must be signed in to change notification settings - Fork 64
Code Style Guide
Rory Powis edited this page Jan 11, 2016
·
1 revision
"All code in any code-base should look like a single person typed it, no matter how many people contributed." - Rick Waldron
- Use Editorconfig when possible.
- Two space indents. Don't use tabs anywhere.
- No trailing whitespace, except in markdown files where a linebreak must be forced.
- Files must end in a new line
- 100% test coverage is a good goal to strive for, even if it's not always practical to reach it.
- Unit tests are written following the "it should..." format