Hi, I've noticed that several rules, for examples no-trailing-spaces and no-multiple-empty-lines are not mentioned anywhere in the readme. Is this intentional? If not, I'd be happy to make a PR that includes the missing ones I can find in the readme. It'd be nice to have a curated list of the rules the guide enforces without having to dig into the .js files.
Sure, there's no particular reason. (no-trailing-spaces is just a best practice in all languages from time immemorial)
A PR would be helpful.
Now that #1798 is merged, what more do you think needs to be done to close this?
@ljharb I figure this can probably be closed. I opened this mainly to raise a question - which has been answered - and the key rules I was looking for are now documented. I might open another similar PR in the coming weeks to cover a few more rules and can reference this issue, but I don't think it needs to be left open unless you see documenting every rule as something of a priority.
Sounds great!
If you come up with a concrete list - with or without a PR (which are always appreciated) - then let's reopen this. Until then, I'll close it.