Linting ignored files triggers a warning

[mgol]

See eslint/eslint#905 for the description of the problem & discussion around it.

Basically, if you want to have filest passed to the eslint task usable for usage with grunt-newer, you need to pass files, not directories. But if you pass files and some of them are in .eslintignore, ESLint triggers a warning. This can seriously flood the console with warnings not applicable here; it's enough to e.g. pass app/**/*.js to the eslint task and have app/vendor/** in .eslintignore.

@nzakas proposed to add the --silent option to ignore warnings which would make this issue disappear but would also make all other warnings disappear.

Do you have a better idea how to solve this problem? Input welcome!

[sindresorhus]

The solution is for ESLint to have a real programmatic API so I don't have to use the CLI interface.

It should just accept and array of file paths (not directories!) and options and have events for different things like warnings. That way we consumer can decide what to show.

[nzakas]

If you have a proposal for what such an API would look like, please file an
issue. I'm doing a lot of refactoring so now would be the best time to
chime in.
​

[sindresorhus]

@nzakas done: eslint/eslint#935

[mgol]

@sindresorhus Now that eslint/eslint#935 is resolved (and ESLint 0.7.1 released), this issue should be solvable, right?

[nzakas]

This API isn't exposed publicly yet, it will be in 0.8.0.​

[pigulla]

Any updates on this?

[nzakas]

The API has been available in ESLint for a while now. https://eslint.org/docs/developer-guide/nodejs-api.html

[sindresorhus]

@pigulla #34 (comment)

[ratherblue]

Did a flag for this specific functionality ever get added? gulp-eslint has warnFileIgnored but I didn't see a similar option for grunt-eslint. The ignored files are still showing up as warnings when I test this