Naming/FileName with ExpectMatchingDefinition and CheckDefinitionPathHierarchy does not enforce in custom folders

[grosser]

Expected behavior

Naming/FileName:
  ExpectMatchingDefinition: true
  CheckDefinitionPathHierarchy: true

and

# something/bar.rb
module Foo
  class Bar

should be invalid because something != Bar

Actual behavior

it is valid (nothing with --debug either)

Steps to reproduce the problem

see expected

RuboCop version

1.22.3 (using Parser 3.0.2.0, rubocop-ast 1.12.0, running on ruby 2.6.5 x86_64-darwin19)

Misc

I tried poking around in lib/rubocop/cop/naming/file_name.rb but none of the methods in there are getting called if the filename matches the expected constant (also tried with --cache=false)

[splattael]

I can reproduce it with:

$ tree
.
├── lol
│   └── something
│       └── bar.rb
├── lib
│   └── something
│       └── bar.rb
└── something
    └── bar.rb

5 directories, 3 files

$ cat $(find . -name "*.rb")
module Foo
  class Bar
  end
end
module Foo
  class Bar
  end
end
module Foo
  class Bar
  end
end

$ rubocop -v
1.22.3

$ rubocop --only Naming/FileName .
Inspecting 3 files
C..

Offenses:

lib/something/bar.rb:1:1: C: Naming/FileName: bar.rb should define a class or module called Something::Bar.
module Foo
^

3 files inspected, 1 offense detected

RuboCop only detects a single offenses for code which is inside lib (or test, spec or src). Code outside of this structure (e.g. lol/) won't be detected.

Edit: I've added the actual directory structure 🤦

[grosser]

Finally got that working by hacking the gem and using UseCache: false ... so yeah can confirm that works, now just need a way to modify it :D

[grosser]

opened #10224 to fix