GNOME Bugzilla – Bug 790834
Fix eslint not showing any warning
Last modified: 2017-11-26 02:24:06 UTC
If you edit a JS file in node_modules/* (eg a library that's bundled with your project), the eslint plugin crashes because eslint returns a fatal message indicating that the file is ignored.
Created attachment 364398 [details] [review] eslint: Don't crash if eslint message does not contain a line Just skip the message and process the rest of the output
Created attachment 364399 [details] [review] eslint: tell eslint not to ignore files in node_modules/* eslint "helpfully" ignores all files in node_modules/* and bower_components/* by default (even if --no-ignore is passed). This is fine for command line usage, but in Builder, assume that if the user opens a file, they really want diagnostics for that file, regardless of its location.
Review of attachment 364398 [details] [review]: LGTM
Review of attachment 364399 [details] [review]: Seems reasonable to me
Thanks for the review, pushed!