[Fix #2044] Fix unintended document changes caused by default Rake task #2047
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes unintended document changes caused by default Rake task.
Problem
The default task causes
RuboCop::Config
to end up in an unexpected state wheninternal_investigation
task is executed beforegenerate_cops_documentation
task. This is due to the fact that plugins are already loaded when RuboCop is executed as part ofinternal_investigation
.Solution
This change preemptively determines whether configuration adjustments are necessary based on whether
rubocop-rspec
plugin has already been loaded.Additional Information
Since this logic should ideally be encapsulated within
CopsDocumentationGenerator
, it is expected to become unnecessary in the future once the API design and implementation ofCopsDocumentationGenerator
class are complete. For now, this serves as a temporary workaround.Fixes #2044.
Before submitting the PR make sure the following are checked:
master
(if not - rebase it).CHANGELOG.md
if the new code introduces user-observable changes.bundle exec rake
) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).If you have created a new cop:
config/default.yml
.Enabled: pending
inconfig/default.yml
.Enabled: true
in.rubocop.yml
.VersionAdded: "<<next>>"
indefault/config.yml
.If you have modified an existing cop's configuration options:
VersionChanged: "<<next>>"
inconfig/default.yml
.