ESLint initializer should be optional
hon2a opened this issue · 1 comments
JavaScript linting is a concern shared by all packages, large and small, regardless of what's in them and whether that includes the use of Quadro. While getting linting out-of-the-box through the Quadro es_lint
initializer might be helpful for packages purely based on the framework, there are others (apps) where Quadro is just part of the equation. And then there are packages completely without Quadro (the new front-end related packages). These should be standardised as well and they are - outside of Quadro.
In packages where the both worlds meet and the linting is done simply with eslint-cli
, it's undesirable for Quadro to duplicate the process and it may even cause errors (or force such packages to use versions of linting tools that are out of sync with the outer suite of packages). Therefore the linting done by Quadro should be made optional, so that the packages already taking care of it through other means don't collide with Quadro.
Turns out that turning off initializers in general is already possible and I just didn't know about it.
initializers:
es_lint: false