-
-
Notifications
You must be signed in to change notification settings - Fork 16
Closed
Description
1. Summary
It would be nice if prefer-arrow-functions will have the predefined configuration as another ESLint plugins.
2. Example of expected behavior
All ESLint plugins that I use have all and/or recommended predefined configuration.
export default [
compat.configs["flat/recommended"],
eslintPluginUnicorn.configs.all,
nounsanitized.configs.recommended,
perfectionist.configs["recommended-natural"],
pluginJs.configs.all,
sonarjs.configs.recommended, {
// My settings
},
];It would be nice if prefer-arrow-functions will have the similar predefined configuration:
compat.configs["flat/recommended"],
+ eslintPluginPreferArrowFunctions.configs.all
eslintPluginUnicorn.configs.all,
In this case, users will not be required to add default rules from the predefined configuration eslintPluginPreferArrowFunctions.configs.all to their eslint.config.mjs files.
3. Justification
Automation.
- prefer-arrow-functions behavior. When I installed prefer-arrow-functions first time, the plugin have 5 rules. Currently, it has 2 new rules
allowedNamesandallowObjectProperties. I need manually add these rules to my configuration file. But users aren’t tracking changes of prefer-arrow-functions and may not find out about the addition of new rules. - Another ESLint plugins behavior. Plugin developers added a new rule → they added this rule to the predefined configuration → a user download an updated version of the plugin → a new rule automatically applied for user, he doesn’t need manually add the rule to his configuration file.
It would be nice if prefer-arrow-functions will have the behavior as another plugins.
Thanks.
SchroederSteffennbouvrette
Metadata
Metadata
Assignees
Labels
No labels