It would be useful to have a dev-mode or watch mode where errors downgraded to warnings so your test suite runs when practicing TDD.....
When this feature is available, the no-console rule should be upgraded back up to an error.
This issue, https://github.com/uber/lint-trap/issues/64 , is related because both might be implementable the same way: via an only flag which can either be warning or error:
--only=error or --only=warning
Question: Is process.env.NODE_ENV an appropriate way to set everything to warning?
It would be useful to have a dev-mode or watch mode where errors downgraded to warnings so your test suite runs when practicing TDD.....
When this feature is available, the
no-consolerule should be upgraded back up to an error.This issue, https://github.com/uber/lint-trap/issues/64 , is related because both might be implementable the same way: via an only flag which can either be
warningorerror:--only=erroror--only=warningQuestion: Is process.env.NODE_ENV an appropriate way to set everything to warning?