nrwl
I'd like to not extend nx shared eslint configs
- [ ] I'd be willing to implement this feature (contributing guide)
Description
I'd like to not extend nx shared eslint configs
Motivation
We already have a pretty solid set of ESLint configurations through our own shared configs. However, because this tool extends entire configs under overrides in sub-projects, it ends up overriding a lot of stricter rules that we set in a top-level .eslintrc file. And overrides them with some more lenient/warn defaults.
We end up having to clean up after each generator usage, and when missed, it can accumulate for months, building technical debt, until it's finally noticed and we have to go back and fix all of the now-failing lint.
Last I checked, @nx/angular isn't even even introducing new rules, it's more of a shared configs itself than a plugin.
Suggested Implementation
???
Alternate Implementations
For now I'm straight up patching this out of the add-linting generator in the NX package on install using patch-package. And since it's conflicting with our shared configs, I'm doing it as part of the shared config package's postInstall.
