-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
docs: use consistent naming recommendation #20250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mdjermanovic
merged 2 commits into
eslint:main
from
kitsunekyo:docs/inconsistent-legacy-naming-recommendation
Oct 30, 2025
Merged
docs: use consistent naming recommendation #20250
mdjermanovic
merged 2 commits into
eslint:main
from
kitsunekyo:docs/inconsistent-legacy-naming-recommendation
Oct 30, 2025
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docs-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
The docs pages extend/plugin-migration-flat-config#backwards-compatibility and extend/plugins#backwards-compatibility-for-legacy-configs both recommended different namings for legacy configurations.
While the former page called for a suffix
-legacy, the latter recommends a prefix withlegacy-.The docs line recommending
legacy-as prefix had a more recent commit (7 months vs 2 years) and both eslint-plugin-vitest and eslint-plugin-package-json use this naming, so I opted to keep this version.Is there anything you'd like reviewers to focus on?
Please check whether the naming convention is the one you want to go with.