Plugins define new ESLint rules, but they can also ship with a configuration (e.g. recommended config for those custom rules).
Is it considered bad practice to have that config also list out rules outside of the ones that the plugin defines? In other words, could a `eslint-plugin-foo` include a config that has settings for the plugin rules, plus the following: 1) configuration for ESLint default rules 2) configuration for other custom rules (this would require that the plugin pull in other plugins as dependencies) I would think a separate `eslint-config-foo` repo that pulls in and configures the rules from `eslint-plugin-foo`, possibly from other plugins, as well as default rules would be preferable, but I've seen it done both ways. Any best practice here? -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
