Getting a list of jshint warnings

[massimiliano-mantione]

The plugin is working, however it "only" marks the points in the editor where jshint found a problem, without even a hint of whether there were problems or not.
I did not find a command like "jump to next-previous warning" so in a large file I cannot even find the warnings...
Would it be possible to make the plugin open a panel with the list of problems that jshint has found?
Or at least have a message that gives the number of warnings and the ability to navigate through them.

Maybe the minimal way of doing it would be a pair of "go to next-previous jshint warning" commands, each of which would

• go to the warning, and
• print something like "Warning number XXX of YYY", or if there are no warnings, "No jshint warnings in this file".

And have the "run jshint" command automatically execute the "go to next jshint warning" command so that the user

• knows if there are warnings, and
• immediately sees the first one.

This would not require any separate panel.

And yes, I know I should try to do it myself, but here comes the second question: is it mandatory to write such an extension in Clojurescript (creating a panel and filling it with a list of "errors", or anyway references to locations in an editor window), or is there a pure Javascript API for it? (I did not find it...)

[mariusa]

Also, would please add some intructions to the README on how to use the plugin?
I don't see any warnings, as Massimiliano mentioned, and I doubt the code is 100% perfect.

Thanks

[massimiliano-mantione]

Also, would please add some intructions to the README on how to use the
plugin?
I don't see any warnings, as Massimiliano mentioned, and I doubt the code
is 100% perfect.

Note that I do see the warnings.
My problem is just that in a 4k lines file finding them is impossible.

Cheers,
Massi

[cldwalker]

Looking through old issues and found this.
@massimiliano-mantione I am able to see inline hints on the appropriate lines for a large file. Can you verify this is still an issue with the latest LT and just released plugin update?
@mariusa Usage has been added to readme