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
As can be seen in https://github.com/bbatsov/rubocop/blob/master/spec/rubocop/cli_spec.rb#L1117 the paths for Include, and presumably for Exclude as well, are currently interpreted by RuboCop as relative to the current directory. They should be relative to the position of the configuration file (usually .rubocop.yml) just like AllCops: Includes and AllCops: Excludes already are.
The text was updated successfully, but these errors were encountered:
In a file named .rubocop.yml, the paths are relative to the directory
where the configuration file is. In a configuration file with a
different name, such as default.yml, the paths are relative to the
.rubocop.yml file inheriting from it, or if there's no such file,
the current directory.
This problem was discovered in #891.
As can be seen in https://github.com/bbatsov/rubocop/blob/master/spec/rubocop/cli_spec.rb#L1117 the paths for
Include
, and presumably forExclude
as well, are currently interpreted by RuboCop as relative to the current directory. They should be relative to the position of the configuration file (usually.rubocop.yml
) just likeAllCops: Includes
andAllCops: Excludes
already are.The text was updated successfully, but these errors were encountered: