docs: explain mergeConfig skips null/undefined (#22325)
Open
Nobody has claimed this yet.
sync
- Dominant language
- No language data
- Stars
- 9
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
New updates on head repo.
https://github.com/vitejs/vite/commit/2151f701dc98270c905c540b209fb6d23d53d3ad
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Vite commit, then locate the German documentation page covering mergeConfig. Add an explanation that null and undefined values are skipped, and confirm the wording matches the behavior described by the commit.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100