Files with the same name (without extensions) are not parsable #955
Description
Moving this out of #890 as it's an issue we need to track.
Comment by @toddbluhm:
The issue appears to occur when I have two files with the same name (fixture.ts & fixture.js) in the same folder (src). It only picks up the .ts file and will not pick up the .js file. Instead, it gives the error that fixture.js was not included in the project.
I can confirm that deleting fixture.ts and keeping fixture.js causes the "not included in project" error to go away. So by deleting either fixture.ts or fixture.js causes the "not included in project" error to go away. Keeping both files, causes the error to show up.
**tsconfig.json**
**tsconfig.eslint.json**
{
"extends": "./tsconfig.json",
"compilerOptions": {
"allowJs": true,
"checkJs": true
},
"include": [
"src/**/*",
"*.ts",
"*.js"
]
}**.eslintrc.json**
{
"extends": "./lib/index.js",
"parserOptions": {
"project": "./tsconfig.eslint.json"
}
}**Example file paths that are throwing errors**
/Users/toddbluhm/Development/Github/eslint-config-standard-with-typescript/src/fixture.js- Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser.
The file does not match your project config: /Users/toddbluhm/Development/Github/eslint-config-standard-with-typescript/src/fixture.js.
The file must be included in at least one of the projects provided
- Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser.
Versions
| package | version |
|---|---|
@typescript-eslint/eslint-plugin |
2.0.0 & 2.0.1-alpha.27 |
@typescript-eslint/parser |
2.0.0 & 2.0.1-alpha.27 |
TypeScript |
3.5.3 |
node |
10.15.0 |
{ "extends": "./node_modules/tsconfigs/universal", "compilerOptions": { "esModuleInterop": true, "importHelpers": false } }