Closed EvHaus closed 10 years ago
To be clear, are you saying the only thing missing is (W015)? That is an error code of some sort?
On Sun, Nov 24, 2013 at 3:02 PM, Globex Designs, Inc < notifications@github.com> wrote:
It would be great if brackets-jshint could display the warning and error codes for each JSHint line similar to what grunt-contrib-jshint does. ie:
26 (W015) Expected 'case' to have an indentation at 25 instead at 29.
instead of the current
26 Expected 'case' to have an indentation at 25 instead at 29.
It would make it easier to identify the specific error/warning types.
— Reply to this email directly or view it on GitHubhttps://github.com/cfjedimaster/brackets-jshint/issues/21 .
Raymond Camden, Adobe Developer Evangelist
Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster
Correct. Each error type has a code in JSHint (as far as I know). It would be great to be able to see that.
I'm not sure how useful it would be. I noticed in the docs they barely use it themselves. But - it would be harmless to add. I may add it to the end of the description though.
On Sun, Nov 24, 2013 at 4:57 PM, Globex Designs, Inc < notifications@github.com> wrote:
Correct. Each error type has a code in JSHint (as far as I know). It would be great to be able to see that.
— Reply to this email directly or view it on GitHubhttps://github.com/cfjedimaster/brackets-jshint/issues/21#issuecomment-29168921 .
Raymond Camden, Adobe Developer Evangelist
Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster
I find it makes it easier to search for the errors online. Especially when you're just starting with linting. Often times you'll want to find examples of how to fix your issue and to better understand the problem. It's much easier to look up the code than have to copy/paste the full error message. Pretty trivial -- but if it's a small task on your end, would be a great addition I think.
Thank you!
I'll get to it - but not till after Thanksgiving.
On Mon, Nov 25, 2013 at 9:44 AM, Globex Designs, Inc < notifications@github.com> wrote:
I find it makes it easier to search for the errors online. Especially when you're just starting with linting. Often times you'll want to find examples of how to fix your issue and to better understand the problem. It's much easier to look up the code than have to copy/paste the full error message. Pretty trivial -- but if it's a small task on your end, would be a great addition I think.
Thank you!
— Reply to this email directly or view it on GitHubhttps://github.com/cfjedimaster/brackets-jshint/issues/21#issuecomment-29211817 .
Raymond Camden, Adobe Developer Evangelist
Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster
Fixed with last push.
Confirmed. Thank you!
It would be great if brackets-jshint could display the warning and error codes for each JSHint line similar to what grunt-contrib-jshint does. ie:
26 (W015) Expected 'case' to have an indentation at 25 instead at 29.
instead of the current
26 Expected 'case' to have an indentation at 25 instead at 29.
It would make it easier to identify the specific error/warning types.