search

cfjedimaster / brackets-jshint

Adds JSHint support to Brackets
MIT License
130 stars 41 forks source link

Inline notifications for errors #30

Closed mikkotikkanen closed 10 years ago

mikkotikkanen commented 10 years ago

Instead of the big ol' screen popping up, how about marking the lines with exclamation marks next to the line number or different color?

This way, when you are in the mids of writing new things which are broken because they aren't finished yet, you wouldn't lose screen realestate & focus for the JSHint screen every time you save.

Something like this would bind the notifications better to the workflow - ie. get things together first, then clean up the linting/hinting problems. So, by definition, syntax errors etc. should be more visible than lint/hint errors. By changing them to something less visible, the human brain sorts out the priority by itself. :)

cfjedimaster commented 10 years ago

Right now JSHint uses the built in linting API which handles all the UI for you. I can see some merit in a UI like that, but if I were you I'd file this against the main Brackets project.

mikkotikkanen commented 10 years ago

Oh, ok.

mikkotikkanen commented 10 years ago

Reported to Brackets

dandv commented 10 years ago

+1 for this. WebStorm displays JSHint warnings inline, so you see them right away as you type.