Open StephenGregory opened 9 years ago
I suspect the issue is on this line, wherein it is assumed that the settings file in in JSON.
How after deferring the parsing of the file to ESLint (see getConfigForFile()) ?
@StephenGregory thanks for logging this issue. Currently, interactive linter only supports json formatted settings files. I am not totally against supporting YAML. Would you be willing to put together a PR?
Sure! For reference, how have you gone about getting the single eslint.js
in your repo (and others)?
Update: I'm thinking those dependencies can be pulled in with npm
instead. The reason being is that the dependencies would be more clearly defined, with the added benefit of being to pull in ESLint's config parser.
Yes, I have hit the issue when I switched from JSHint to ESLint, generating (with eslint --init
) a Yaml file.
I switched to Json, but I would prefer to use Yaml as it allows comments...
BTW (slightly unrelated, I can create a new issue if needed), how can we cleanly update the ESLint version? Some options seems to be unrecognized or limited (eg. line ending and brace placement).
Description
ESLint supports .eslintrc being written in YAML. The Interactive Linter displays and error message and cannot use the file.
Steps to reproduce
Configure
brackets.json
appropriately:Create a
.eslintrc
file in your project directory with the following content:An alert prompt displays the following: