-
- Tabs vs spaces (2 spaces please!)
- Semicolons please
- Let's stick to a standard in markdown (interestingly, @iteles uses `_underscores_` for _italic_ and @nelsonic uses `*single asterisks*`)
- Ful…
-
Some iteration upon this perhaps?
![semistandard](https://cloud.githubusercontent.com/assets/17499/6894004/34f2c676-d72e-11e4-86d5-a49365679f9f.png)
-
I think this is an error with contrib-standard as well - semistandard outputs lint errors in all files in the current directory (not just the current one), so the linter shows errrors for all files in…
-
Need to write some tests for scenevr-web, including onces that make sure the bundle compiles correctly, I forgot to add a template to the repo and the build has been broken for two days, need to avoid…
-
https://github.com/Flet/SublimeLinter-contrib-semistandard
Thanks again!
-
It doesn't mean this style checker is any less “standard” just because someone grabbed a fancier name first.
Checking for `standard` in npm scripts doesn't mean checking for someone else's standard, …
-
This would make debugging #220, and probably many future issues, much easier. Could be implemented as a config setting, a CLI option, or both.
-
> It favours flexibility over strictness for things like multi-line lists and single-line rulesets, and tries to avoid potentially divisive rules.
Is fine and all, but it's not a _standard_.
Flexibl…
-
```
➜ nanomsg git:(formatting) ✗ semistandard -h
Usage:
standard
Flags:
-v, --verbose Show error codes (so you can ignore specific rules)
--stdin Force processing …
-
Best practice to have a `CHANGELOG.md`, preferably using [standard formatting](http://keepachangelog.com/)