You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This fixes another problem that's similar to the one reported in rubocop#7790. The
problem is still that configuration is read and cached when we validate options
vs configuration. By acting on all options first, we make sure that the first
time we read configuration, it's done according to the given options.
Specifically, it's the --force-default-config option that's now being
respected.
It seems like the
--parallel
-switch breaks using--force-default-config
wheninherited_from
uses a broken / unavailable URL.This is probably related to #7790
Expected behavior
In a project with a local
.rubocop.yml
, runningshould ignore the config given in
.rubocop.yml
Actual behavior
still uses the local
.rubocop.yml
. The same applies to using--config /dev/null
instead of--force-default-config
Steps to reproduce the problem
.rubocop.yml
configinherit_from
with an unresolvable URL.--force-default-config
and--force-default-config --parallel
Alternatively use the example project at https://github.com/defsprite/rubocop-bug
RuboCop version
The text was updated successfully, but these errors were encountered: