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
Run yarn e2e, see that the lint step is flagging no-console for instances of console.warn, even though that is allowed by the local setting.
What is expected?
I expect local rules to take precedence over the built-in rules.
What is actually happening?
Currently, even if users define their own settings for no-debugger or no-console, these are ignored. I personally think an out-of-the-box no-console rule is a little too opinionated, even if it only restricted console.log. I personally never want to see console.log in committed code, but I've seen others use it intentionally.
The text was updated successfully, but these errors were encountered:
Version
3.0.0-beta.10
Reproduction link
https://github.com/chrisvfritz/vue-enterprise-boilerplate
Steps to reproduce
Run
yarn e2e
, see that the lint step is flaggingno-console
for instances ofconsole.warn
, even though that is allowed by the local setting.What is expected?
I expect local rules to take precedence over the built-in rules.
What is actually happening?
Currently, even if users define their own settings for
no-debugger
orno-console
, these are ignored. I personally think an out-of-the-boxno-console
rule is a little too opinionated, even if it only restrictedconsole.log
. I personally never want to seeconsole.log
in committed code, but I've seen others use it intentionally.The text was updated successfully, but these errors were encountered: