docs: use consistent naming recommendation #20250
Merged
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. |
497f5e4 to
d499064
Compare
d499064 to
4d23bd5
Compare
Member
|
Thanks for catching this inconsistency. We should definitely align these recommendations. |
Co-authored-by: Milos Djermanovic <[email protected]>
lumirlumir
approved these changes
Oct 30, 2025
Member
lumirlumir
left a comment
There was a problem hiding this comment.
LGTM, thanks!
Would like @mdjermanovic to verify before merging.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.