Reasoning decisions behind rules?

[dorner]

I'm looking at adapting Standard in new and existing codebases in our company. One thing that's throwing me off is that there doesn't seem to be a central place to go to find out why decisions were made. Rubocop itself has the Ruby Style Guide as the source of truth for most of its defaults. How can I find out why Standard decided to do or not do something?

I saw there was a previous issue that was "closed as completed" but no action seems to actually have been taken: #568 

Any further info would be greatly appreciated!

[searls]

Hi @dorner. It's true we haven't documented all this. It'd be nice to, but I'm not sure who would find it worth their time to do. Most people start using Standard, get mad about 3-5 things, then over the course of a couple weeks get used to it, and "Standard Style" just sorta seeps in as if by osmosis.

We have a loose arrangement of principles we use to decide on rules, and I think we should publish those, we just haven't gotten them into a tidy format yet