Feature Proposal: Make use of local/global ESLint config when generating code

[designorant]

This proposal is trigerred by @jeremyjs message on the FeathersJS Slack:

If I want to modify the feathers generators to follow my style guide, what's the best way to go about it?

Would I be right to think that in theory it should be possible to pass a config that would modify the generated code accordingly? It wouldn't work with all of the rules, but could definitely help with the basics. This could work somewhat low level, or simply by using the --fix argument on the already generated code.

[SBoudrias]

You can have a pre-processor run over the files before they're committed to disk that would make them follow their styleguide. See Transform output files through streams for more details.

That being said, the main issue you'll have is that eslint don't fix all the issues or the rules inside the eslint config. So would that ever be good enough?

[jeremyjs]

@SBoudrias: Personally, my use case is as @designorant says, but I'm willing to compromise by providing custom overrides for any files that aren't totally fixed by a preprocessor. The only problem then is keeping my overrides up to date with the latest releases.

[github-actions]

This issue is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 5 days