cargosense / rubocop-cargosense Goto Github PK

Similar to rubocop-airbnb's config folder, we could/should/will break out this gem's rules into discrete namespace-specific configuration files. Doing so will prevent config/default.yml from growing unmanageable as we add more gems and custom configuration (e.g. rubocop-rails, rubocop-rspec). config/default.yml should serve as a clown car of sorts and inherit from all of the namespace-specific configuration files.

A recommended layout (within ./config):

• default.yml (the whole thing)
• rubocop.yml (inherits all namespaced files configureable in RuboCop)
• rubocop-layout.yml (Layout/* rules from the rubocop gem)
• rubocop-performance.yml (Performance/* rules from the rubocop-performance gem)
• etc. etc. etc.

As a secondary bonus, this configuration change will also allow consumers to pick-and-choose configuration files within their projects. Documentation should be updated to reflect this capability while also strongly encouraging the existing preferred usage (inherit the whole thing and go about your day).