4 ms·
If you're going to have your team agree on any style rules at all, then automated style checking is the only way to go. Let the computer yell at people so you
by kevincennis 12y ago
If you're going to have your team agree on any style rules at all, then automated style checking is the only way to go.
Let the computer yell at people so you don't have to.
Nobody wants to be the pedantic jerk who has to leave comments on a PR about whitespace or single vs double quotes.
When you use an automated style checker, you presumably catch those errors before a PR gets submitted and nobody ever has to be the bad guy/girl.
- akbar501 12y ago> automated style checking is the only way to go Absolutely. We've found automated style checking also improves quality and efficiency. Even the "pedantic jerk" can miss small style issues that are easily caught by tooling. For anyone wondering what tools. The most common for JS are JSHint and JSCS. Then use Grunt or Gulp combined with a watch to check a file each time a change is saved. Lastly, use a precommit hook (or similar) to check again before code is committed into the repo.