4 ms·
I'd highly recommend using something like eslint, which can be integrated into editors and CI flows to assist with most of the style guide choices (at least the
by andrewstuart2 10y ago
I'd highly recommend using something like eslint, which can be integrated into editors and CI flows to assist with most of the style guide choices (at least the never/always kind) that your organization makes.
Use some style guide as a base and then agree on your own internal exceptions/additions as a team, then just implement those rules, and eslint can let you know when you've forgotten something.
Personally, I find the editor (via Syntastic in vim) integration most helpful since it's more of a warning and not an overbearing release gate.
- r0m4n0 10y agoYep, well aware and utilize plenty of linting. Javascript style is one thing, Angular (amongst other frameworks) leave much room for different styles of structure, modularization, dos/don'ts. It's important to agree on one set of framework styles as a team otherwise consistency of patterns could be a nightmare. Having an official style guide (which didn't exist with Angular 1) simplifies this...