Skip to content
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

Error when defining a custom location of configfile and analyzing files inside same location #1946

Open
gian1200 opened this issue Nov 1, 2024 · 0 comments
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@gian1200
Copy link

gian1200 commented Nov 1, 2024

Continuation of #1932

Issue happens when setting config file in a custom location (e.g. <project-path>\.config\eslint.config.mjs)

I think I've pin point the issue. It happens only for files inside .config folder. For any file outside, VSCode-ESLint works fine.

Steps to reproduce:

  1. git clone reproducer
  2. cd reproduce-vscode-eslint-issue and npm install inside the root folder
  3. code . --> open the project on VSCode and make sure vscode-eslint is enabled (wait for everything to load). If not loaded, a VSCode reload might be necessary.
  4. Open files for testing:
    • src/dummy.mjs: It is flagged correctly by VSCode-ESLint
    • .config/anotherDummyFile.mjs: This file is not flagged at all (see Output for error)
  5. Execute npm run eslint: both files are correctly flagged
@dbaeumer dbaeumer added the bug Issue identified by VS Code Team member as probable bug label Nov 4, 2024
@dbaeumer dbaeumer added this to the Next milestone Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants