Feature: Verbose output about eslint-find-rules HOT 9 CLOSED

Yeah I think we can skip silly completely, but verbose is sth. I'd really like to have in.

from eslint-find-rules.

Another thing that came into my mind, when making the tabular output / sorting the rules' names alphabetically:
We probably should also group those rules, like in a batch of rules for eslint (default) and all loaded plugins eslint-plugin-import etc. ...

from eslint-find-rules.

How should we assign the output to different log levels?
By default, npmlog (I spelled it wrong in the op) comes with these log levels:

• silly: I think this will be unused, but could eventually be used to simply log everything.
• verbose: Print things like "there's no rule unconfigured" (relates to the original package's issue #24.
• info: I think this one should become the default output level.
• http: we do not make any http request, so it'll stay unused.
• warn & error: obviously as usual, when there's sth that went wrong.

Any other ideas? Did I miss anything?

from eslint-find-rules.

Sounds good!

Wondering if silly and verbose should be combined.

from eslint-find-rules.

We might want to address #9 along with this.

from eslint-find-rules.

Yep

from eslint-find-rules.

Go for it.

from eslint-find-rules.

@ta2edchimp do you think we can close this issue?

from eslint-find-rules.

Yep.

from eslint-find-rules.