tests always resolve to project .eslintignore
See original GitHub issueWhen running node Makefile.js test
the pwd of the tests is the top directory of the repository. The contained .eslintignore
file is taken by IgnoredPaths as default when no other file was specified. Independent of the usage of a duplicated fixture directory, always the .eslintignore
file from pwd is used.
FileFinder is able to handle the context switch, but no options are passed by IgnoredPaths yet.
IMO this could be resolved by modifying tests only to either
process.chdir
to a generated test directory (like some of the tests already do)- always specify an
.eslintignore
file viaignorePath
option (when it does not exist, no lookup will occur)
<bountysource-plugin>
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Issue Analytics
- State:
- Created 8 years ago
- Comments:14 (13 by maintainers)
Top Results From Across the Web
typescript-eslint/parser doesn't ignore files, which is excluded ...
In case of project is specified within parserOptions, @typescript-eslint/parser doesn't ignore files, which is excluded by/in tsconfig.json.
Read more >How do I resolve new ESLint errors in my Cloud Functions ...
js/npm ... I'm currently trying to build a mobile app backend with Firebase for a university project. I use node.js and write, not...
Read more >Ignoring Code - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >eslint/eslint - Gitter
More precisely, ESLint v6 resolves plugins relative to the end user's project by default, and always resolves shareable configs and parsers relative to...
Read more >eslintignore file doesn't seem to be working
In my unit test project for instance, I'm using the filter to ignore absolutely all js files and it's still pulling in errors/warnings...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Assuming that this issue is not being worked on, I’ll take a look at it, until somebody says not to. I expect to have something to report within 2 days.
I’m closing this issue since it’s not clear if it’s a problem anymore, and if it is a problem it wouldn’t be affecting users (only people working on the ESLint repo itself).