If there’s a parent component that has some data that it expects to always receive from its children, then that data should be in the parent’s state and the children should receive it as props. Even if it’s an unknown number of children. Don’t muck with useContext for basic inheritance stuff, you’ll mess with the render cycle for no good reason.
Now, if we’re talking about a very distant “top” component, that’s fine, it’s what it was made for. Although many people end up using stores if it’s some data with broad impact (like user data)
deleted by creator
I think you’re being down voted because context should be used sparingly. You can pass data back up the parent chain through prop functions.
deleted by creator
If there’s a parent component that has some data that it expects to always receive from its children, then that data should be in the parent’s state and the children should receive it as props. Even if it’s an unknown number of children. Don’t muck with useContext for basic inheritance stuff, you’ll mess with the render cycle for no good reason.
Now, if we’re talking about a very distant “top” component, that’s fine, it’s what it was made for. Although many people end up using stores if it’s some data with broad impact (like user data)