You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requesting to add support for this option supported by vscode-eslint, but not by this LSP-eslint. To showcase the need, assume a workspace with multiple sub-projects which each have their own configs and at least one having a eslint config that fails to parse:
module1/.eslintrc.js // this config is broken
module2/.eslintrc.js // this config works
In VSCode with "eslint.workingDirectories": [{"pattern": "*"}]vscode-eslint continues to work in module2, but in LSP-eslint, it refuses to work in module2 because the unrelated config in module1 failed to parse.
Also, I think there would be a nice performance benefit if LSP-eslint would not try to parse unrelated config files.
The text was updated successfully, but these errors were encountered:
Requesting to add support for this option supported by
vscode-eslint
, but not by this LSP-eslint. To showcase the need, assume a workspace with multiple sub-projects which each have their own configs and at least one having a eslint config that fails to parse:In VSCode with
"eslint.workingDirectories": [{"pattern": "*"}]
vscode-eslint
continues to work inmodule2
, but in LSP-eslint, it refuses to work inmodule2
because the unrelated config inmodule1
failed to parse.Also, I think there would be a nice performance benefit if LSP-eslint would not try to parse unrelated config files.
The text was updated successfully, but these errors were encountered: