reactjs / reactjs/react.dev

[Suggestion]: add explanation & illustration for the Note in the 'Passing state deeply with context' chapter

Open
#7,652 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: documentation
Dominant language
JavaScript
Stars
11.8k
Forks
7.9k
Avg merge
1d 11h
Merged PRs (30d)
11

Description

Summary

Currently, in the Note, it says "This example uses heading levels because they show visually how nested components can override context.". However, it is unclear what this sentence means. What does it mean for a nested component to override context? I suspect that 'because they show visually how nested components can override context' is not correct, or if correct, it needs clear explanation what it means, because I personally don't get it (and I don't want to ask GPT to get a wrong answer...).

If left unchanged, this sentence risks confusing millions of learners in my opinion (myself included).

Page

https://react.dev/learn/passing-data-deeply-with-context

Details

The sentence "This example uses heading levels because they show visually how nested components can override context." is not explained. It would be useful to explain this much more explicitly. It's like throwing a sentence at a super abstract level... (which is not helpful for learners).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the “Passing data deeply with context” page linked in the issue and read the Note around the sentence about heading levels and nested components overriding context. Clarify the statement with an explanation and illustration showing what the example demonstrates; done means learners can understand the relationship without needing outside explanation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.