docs: how to author plugins with configs that extend other configs#18753
Merged
nzakas merged 3 commits intoeslint:mainfrom Aug 7, 2024
Merged
docs: how to author plugins with configs that extend other configs#18753nzakas merged 3 commits intoeslint:mainfrom
nzakas merged 3 commits intoeslint:mainfrom
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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)
It's not immediately clear from the current documentation how authors should migrate configs that extend other configs.
According to the full documentation, an array is actually expected, which isn't clear in the migration documentation.
This change updates the documentation to include an array example, and links back to the full documentation.
Is there anything you'd like reviewers to focus on?