Extension somehow ignores options given in package.json about vscode-eslint HOT 9 CLOSED

Not sure what's the difference, but jscs extension works properly with similar setup on the same project.

from vscode-eslint.

Could reproduce. Need to understand why this is the case since we delegate config reading to the eslint node module.

from vscode-eslint.

I've found something. You can repeat my steps by setting breakpoint on line 122 of server.ts.

cli.executeOnText calls cli.getConfigForFile to determine which set of rules to apply (see eslint sources). cli.getConfigforFile('d:\some\path') return config object with empty fields. While cli.getConfigforFile('d:/some/path') (note backslashes) return correct config object. And vscode-languageserver.Files.uriToFilePath return path with backslashes \.

from vscode-eslint.

@hogart: thanks a lot for the tip. Will have a look.

from vscode-eslint.

Actually I'm not sure this is vscode-eslint issue. Back-slashed (\) paths are officially returned from path.normalize, so every node software should know how to handle it. The question is should we raise it to eslint, or create workaround, or may be both? It still bothers me that standalone eslint . command works properly.

from vscode-eslint.

I debugged it again and actually the config in package.json is honored. I used eslint version 1.10.3. The path uses backslashes and the actual resolving is happening from the package.json file.,

from vscode-eslint.

@hogart I tried to clone the repository from your first comment but it is not public. If you provide me access to the code or attach a zip with it I will investigate further.

from vscode-eslint.

Very strange, but I can't reproduce it now too.
Probably it was problem of some particular eslint version.

from vscode-eslint.

@hogart thanks. I will close the issue. Pls reopen if you see it again.

from vscode-eslint.