Hound/Rubocop Config

[joe-sharp]

Any chance you can check-in the Rubocop config? The rules that Hound enforces are a bit difficult to predict. If Hound is using its own default config may I suggest going with something closer to what Rubocop uses for defaults? Happy to update the codebase to adhere to the rules as well. Thanks for considering it!

[nickcharlton]

It comes from our guides repo.

I'd like to switch over to standard, which is what we've done everywhere else at some point.

[n-rodriguez]

Hi there! Any news?

[pboling]

#250 switches to rubocop-lts, which is a wrapper around rubocop, standard, and rubocop-gradual (an Evil Martians project). rubocop-lts has a discrete major version customized for every specific minor release of Ruby.

Hound is entirely incompatible with the setup, and suggests making many changes that would result in syntax errors in the code.

• Turn off Hound, or restrict to very basic comments, like "line too long"
• Add style workflow #251 As an alternative, I'll be adding a Style workflow which will enforce style directly in CI.

[nickcharlton]

I'm expecting to have to turn off Hound. I haven't looked at this in a while, but I'd not be against just switching to entire style to follow standard in one go. It's what I did with Administrate: thoughtbot/administrate#2508

[pboling]

My hope is you'll find that going one step further than standard carries many benefits.

I'll setup the style workflow so you can see... but hound will continue to be annoying as hell, and it'll be in a branch off of the same #250 that fixes the build.