Add rubocop about meilisearch-rails HOT 4 CLOSED

Hello @brunoocasali! Thank for starting this huge work!

Do Meilisearch team have a set of rubocop constraints (overrides) to be used already or I'm free to suggest mine?

Nope, not at the moment

After the first execution without any overrides I got: 73 files inspected, 823 offenses detected, 684 offenses auto-correctable probably we will not refactor the entire gem in one big bang PR right? I could submit multiple pull requests with different contexts like (one for specs and so on...)

Yes, do multiple PRs is a good way to handle this issue 🙂

from meilisearch-rails.

Closed thanks to @brunoocasali's PRs in favor of #77 :D

from meilisearch-rails.

@curquiza I've started this locally and I had some concerns about this:

• Do Meilisearch team have a set of rubocop constraints (overrides) to be used already or I'm free to suggest mine?
• After the first execution without any overrides I got: 73 files inspected, 823 offenses detected, 684 offenses auto-correctable probably we will not refactor the entire gem in one big bang PR right? I could submit multiple pull requests with different contexts like (one for specs and so on...)

from meilisearch-rails.

@curquiza I'll try to generate the PR's separately in two ways:

• by directory
• by kind of change

Because if I merge both of the operations at the same PR, probably maintainers will have a bad time finding something relevant, a meaningful change or a problematic one for example.

from meilisearch-rails.