2438 rubocop offenses detected

[bootstraponline]

rubocop should be setup to run automatically on Travis and the code should be updated to follow the style guidelines.

$ rubocop
126 files inspected, 2438 offenses detected

[waynerobinson]

Whilst it's good to develop within a standard, Rubocop's rules are suggestions rather than hard-and-fast and you'll find the vast majority of projects/developers disagree with the application of very large swaths of the default Rubocop default ruleset.

I suggest that a well-tested codebase is much more important than following some arbitrary rules that one developer feels makes up a good Ruby project.

I vote to close this issue.

[bootstraponline]

the vast majority of projects/developers disagree with the application of very large swaths of the default Rubocop default ruleset.

Citation needed. I think that's a false statement.

The Ruby style guide is widely used and rubocop is the result of 153 contributors, not one individual. Within the Sauce Ruby community, which is what's relevant here, rubocop is already being used for both appium's Ruby bindings and the applitools Ruby SDK. The solution to disagreeing with specific rules is to configure the linter, not abandon style checking entirely.

The code base for sauce_ruby is not well tested and is inconsistent in terms of style. Following along with other Sauce Labs initiatives, such as the majority of the appium project (via jscs), and adopting standard code quality tools makes sense. Arguing against linting is not productive.

[bootstraponline]

I suggest that a well-tested codebase is much more important than following some arbitrary rules that one developer feels makes up a good Ruby project.

I agree that testing the codebase is more important than linting, although that shouldn't exclude linting. There's a different issue to address code coverage. #335