Warnings vs Errors about lesshint HOT 5 CLOSED

I totally agree and have actually been thinking about this myself.

Another feature that could follow from this is the ability to specify the severity of a rule violation. Everything defaults to warning but if desired, mark some rule violations as errors and exit with a different code etc.

@kokarn thoughts, ideas?

from lesshint.

👍 to the ability to override severity

from lesshint.

I think @jwilsson is spot on with this and that we all agree that's something that could be useful.

I don't think we should follow jshint tho, add warnings/info to an error object seems a bit backwards and the one letter codes just seems a bit stupid.
@shellscape Do you know why they do single letters?

I think that we should either return a single object with all warnings/error/info on it or a single object with three objects, each containing it's own type.

The more i think about it i like the second alternative a bit more, would be easier to enumerate, could enable handling of specific types differently without having to loop over everything and so on.

from lesshint.

@kokarn no clue why they used single letters - if I had to guess it was left over from jslint or just a style choice. I'm personally OK with an array of result objects, each with their 'state' property. Splitting that up into { warnings: [], errors: [] } is a matter of stylistic preference at that point, or another way to map the data.

I've started work on this on our fork and will submit PRs along the way.

from lesshint.

Closing this, since everything's fine and dandy in #47.

from lesshint.