Probably the hardest part of React, for me, was getting used to the callbacks. Passing data up to the parent component using a function. It's a little difficult to get used to if you haven't encountered it already

[–] [email protected] 11 points 1 year ago

Just shove it in the state! I watched a few react videos over the last TWO WHOLE DAYS, it works!! ;$

[–] [email protected] 2 points 1 year ago

I had gone through Structure and Interpretation of Computer Programming before, and feel like that gave me all the foundational stuff I needed to understand what React is doing. The new third edition is in JavaScript, and while I haven't read it, I imagine that would be an even better match.

[+] [email protected] 1 points 1 year ago* (last edited 1 year ago) (2 children)

[deleted]

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

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 and maybe some relevant methods 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)