Provide a specific error for a rule specification missing a plugin prefix #14027
Labels
accepted
There is consensus among the team that this change meets the criteria for inclusion
archived due to age
This issue has been archived; please open a new issue for any further discussion
core
Relates to ESLint's core APIs and features
enhancement
This change enhances an existing feature of ESLint
Projects
The version of ESLint you are using.
7.18.0
The problem you want to solve.
In trying to enable a rule from a new custom plugin in my
.eslintrc.js
, I made the mistake of forgetting to include the plugin prefix in the specifier:Your take on the correct solution to problem.
It would be nice if a "did you mean?" could be printed at the end of all outputs for each rule that could be matched but for a plugin prefix. Roughly proposing:
Are you willing to submit a pull request to implement this change?
It would be my honor and privilege. ❤️
I dug a little bit and saw that rules are stored in
slots.lastConfigArray.pluginRules
withinLinter
. If a rule is not found, we could check if (semi-pseudocoding here)...The text was updated successfully, but these errors were encountered: