Skip to content
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

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

Open
behanprw opened this issue Feb 26, 2025 · 1 comment

Comments

@behanprw
Copy link

behanprw commented Feb 26, 2025

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).

@karthik-awebon
Copy link
Contributor

karthik-awebon commented Feb 27, 2025

The simple explanation for this line "This example uses heading levels because they show visually how nested components can override context." is The section components are nested, and the child section component overrides the context provided by its parent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants