Default rake task makes unintended changes to docs?

[bquorning]

Running rake locally causes a seemingly unintended change to docs.

I tried “bisecting” the default rake command to find the issue, and interestingly bundle exec rake confirm_config documentation_syntax_check confirm_documentation does not trigger the issue, but bundle exec rake internal_investigation confirm_documentation does:

diff --git a/docs/modules/ROOT/pages/cops_rspec.adoc b/docs/modules/ROOT/pages/cops_rspec.adoc
index 31946294..64666d40 100644
--- a/docs/modules/ROOT/pages/cops_rspec.adoc
+++ b/docs/modules/ROOT/pages/cops_rspec.adoc
@@ -537,17 +537,6 @@ expect { run }
   .and not_change { Foo.baz }
 ----
 
-[#configurable-attributes-rspecchangebyzero]
-=== Configurable attributes
-
-|===
-| Name | Default value | Configurable values
-
-| NegatedMatcher
-| `<none>`
-| 
-|===
-
 [#references-rspecchangebyzero]
 === References

I noticed this on the latest master branch (dac4256) with the most recent dependencies installed.

[bquorning]

cc @pirj, @ydah

[ydah]

I confirmed that if this line is commented out, it does not occur.

rubocop-rspec/tasks/cops_documentation.rake

Line 15 in cd91408

RuboCop::ConfigLoader.inject_defaults!("#{__dir__}/../config/default.yml")

[bquorning]

Ah, so perhaps when rake (default) is run, the inject code and the plugin code is in conflict?

[bquorning]

cc @koic

[koic]

Sorry for taking up your time due to the documentation generation issue. This is a workaround fix, and #2047 has been opened. I plan to address the issue in RuboCop core in the future to allow for simpler usage.

[bquorning]

No worries @koic, and thank you for having a look – and for fixing it too.