-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unignoring directories and their inner files in .eslintignore does not work #11684
Comments
Hi @belochub, thanks for the issue. This does look like a bug, and I think I understand what you're trying to do in your pull request. That said, do you happen to have any documentation (etc.) from node-glob/node-ignore which helps explain the changes in your PR (i.e., what requirements on their side we might have missed)? Not strictly required but would help me understand and review the PR better 😄 |
@platinumazure since #11546 has landed, I've updated my PR, and node-glob is no longer used. As for node-ignore, one of the conventions specified in the documentation is relevant to this issue: https://github.com/kaelzhang/node-ignore#2-filenames-and-dirnames |
Tell us about your environment
What parser (default, Babel-ESLint, etc.) are you using?
default
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
A minimal example that can be used to reproduce the issue:
In the project with the following directory structure:
This is the
.eslintignore
file:Both files
./file.js
and./dir/file.js
contain the following code:01
npx eslint .
What did you expect to happen?
File
./dir/file.js
is linted and an error is reported:What actually happened? Please include the actual, raw output from ESLint.
Are you willing to submit a pull request to fix this bug?
Yes, I have a possible fix for this issue that I would like to submit.
AFAIU, this was broken in #6783 since I've tried this on the ESLint versions that do not include that change (
<3.4.0
), and they seem to be working correctly.The text was updated successfully, but these errors were encountered: