overrides paths don't support `./`

Tell us about your environment

• ESLint Version: v4.16.0
• Node Version: v8.9.1
• npm Version: v5.6.0

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration:

Configuration

mostly irrelevant except:

"overrides": [
  {
    "files": ["./foo.js"],
    "rules": {
      "no-undef": 2,
    },
  },
],

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

foo = 3;

eslint foo.js

What did you expect to happen? A warning.

What actually happened? Please include the actual, raw output from ESLint. No warning.

When I changed ./foo.js to foo.js, I got a warning.

In other words, I think that overrides globs should be able to support leading . or /, like a normal node path + globs.

[ljharb]

It might indeed be obviated by a solution to #9740, but I think it’s a different enough problem that it should be its own issue.

[platinumazure]

Definitely seems like a bug to me, but I don’t know 100% how this is supposed to be designed. I know that we have some special-casing for dotfiles and I’m really hoping that isn’t somehow causing this case.