Decompose config/default.yml
#8
Assignees
Labels
enhancement
New feature or request
Comments
jgarber623
added a commit
that referenced
this issue
Jan 8, 2024
This commit decomposes the default configuration file into namespace- specific configuration files as recommended in #8. For each namespace (in RuboCop proper) and each gem (e.g. rubocop-rake), there's a new YML file configuring that namespace/gem.
jgarber623
added a commit
that referenced
this issue
Jan 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Similar to rubocop-airbnb's
configfolder, we could/should/will break out this gem's rules into discrete namespace-specific configuration files. Doing so will preventconfig/default.ymlfrom growing unmanageable as we add more gems and custom configuration (e.g.rubocop-rails,rubocop-rspec).config/default.ymlshould 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 therubocopgem)rubocop-performance.yml(Performance/*rules from therubocop-performancegem)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).
The text was updated successfully, but these errors were encountered: