You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 7, 2017. It is now read-only.
Haven't dug too deep into this yet, but I noticed everything is logged via console.warn. Would be nice if it were slightly more opinionated, either through the inclusion of .info & .error as well, or style everything with %c & .log.
Gonna take a crack at this, so expect a pull request coming your way. 😏
Amazing tool, by the way. Thanks!
The text was updated successfully, but these errors were encountered:
I originally toyed with the idea of having reporter.warn and reporter.error methods in the rule files but ultimately concluded that what I considered an error, you might only consider a warning (and vise-versa), so I opted not to set error priority in the rule files themselves.
The way HTML Inspector is today, you can basically achieve what you want by overriding the default onComplete function and warn via whatever method you see fit, though perhaps a more declarative way would be nicer.
CSSLint addresses this problem by passing either a 1 or a 2 to the initialization function, which in HTML Inspector's case would look something like this:
Haven't dug too deep into this yet, but I noticed everything is logged via
console.warn
. Would be nice if it were slightly more opinionated, either through the inclusion of.info
&.error
as well, or style everything with%c
&.log
.Gonna take a crack at this, so expect a pull request coming your way. 😏
Amazing tool, by the way. Thanks!
The text was updated successfully, but these errors were encountered: