Plugins are a set of rules distributed as NPM package. Configs are pre-defined
configuration of rules (either default or plugin based). Those two don’t have
much in common. Plugins can include shareable configs, however configs can’t
include plugin rules. So, in short, plugins contain definitions for custom
rules, and configs explain whether those rules should be enabled or disabled
and how they should be configured.
Thanks,
Ilya Volodin
From: [email protected] [mailto:[email protected]] On Behalf Of Tao
Ning
Sent: Wednesday, April 6, 2016 10:06 AM
To: ESLint <[email protected]>
Subject: [ESLint] plugins vs extending configuration
Hi everyone,
I'm new to this awesome tool, ESLint. I have a question which I keeping search
for a while but did't get an answer yet.
Wish you guys could help to explain what is the difference between plugins and
extending configuration? From the docs
http://eslint.org/docs/user-guide/configuring, I feed both of them has the same
functionality which is extends the current rules as well as other configuration
like env, global.
At first I thought extending configuration is like class inheritance in Java,
which give user a base of configuration and then user can add 1+ plugins to add
more rules or other config. But later, I found user can also extending multiple
configurations, this make me feel that plugin and extending configuration are
totally overlapped. So that's say user can just extending configuration instead
of using any plugins.
Thanks for your help.
--
You received this message because you are subscribed to the Google Groups
"ESLint" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected]
<mailto:[email protected]> .
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"ESLint" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
