Open saadq opened 7 years ago
@saadq no that should work. Any chance you could share your product, or put up a repository that reproduces the issue?
I've added a simple repo here. If you run npm run lint
or npm test
, it doesn't display any errors. However, when I open a file that should be ignored in the editor, it displays this:
Some additional details:
linter-js-standard-engine
version: 2.1.0standard
version: ^10.0.2I believe I was also having the same issue when using linter-js-standard
, so it's definitely possible I have something set up incorrectly. Please let me know if this issue isn't happening for you, and then maybe I can try with a clean install of atom with nothing but your package installed.
Thanks, I can reproduce that locally.
Thanks for the report. I have opened a PR #55 with some exploration of the issue. Will have to look at it later. Sorry for the late reply, I've been on vacation and busy at work.
If i have a
packge.json
file like this:Is the package supposed to respect the
ignore
setting I have in thestandard
config? I don't get any errors from runningnpm run lint
becausesome-dir-name
is ignored, but when I open a file insome-dir-name
in Atom, it shows linting errors within the editor. Is there a way to not have the linter run in files that should be ignored?