Loading video...

Video Failed to Load

Go Home

❌ Avoid prop-drilling components in React ✅ Instead embrace the Provider/Consumer pattern using the Context API

48,311 views • 1 year ago •via X (Twitter)

11 Comments

George Moller's profile picture
George Moller1 year ago

I've been working professionally with React for more than 8 years and I compiled all my knowledge into 100+ infographics and 77+ video tutorials just like this one. Check them out ↓

Hunter's profile picture
Hunter1 year ago

While I think this is clean. This pattern has made debugging difficult in my experience with large React apps. With props I can trace them up the tree to find where they're being defined/refined/etc. I can see in the code exactly what's available to a component. With contexts it's not as easy to know what a component has access to, I often end up doing runtime logging to see what's in my context. And it's hard to find where something is being set or added. Again in large apps where naming makes things make grepping an issue tok.

Diego B.'s profile picture
Diego B.1 year ago

In the same file where you create the context, you should use the useContext and export it, so you can have the consumer in there as well. const { addToast } = useToast()

GreLI's profile picture
GreLI1 year ago

As long as you'll do it for forms reacting to every new entered key, the form will be wa-ay too slow. It'll need much effort to memoize everything to prevent sluggishness. Context is good for infrequently changed data.

Fabrizio's profile picture
Fabrizio1 year ago

That would cause Header, Main and Footer to re-render every time a toast is added

Owen Melbourne's profile picture
Owen Melbourne1 year ago

I like what context allows you to do, but wrapping your app in a thousand of them ends up being so 🤮 you start to look at Redux like a god 😂

Enrique Moreno's profile picture
Enrique Moreno1 year ago

Long time no posting. Had a good summer vacation, I guess ;)

George Moller's profile picture
George Moller1 year ago

haha I wish! work has kept me busy Enrique, how are you doing btw?

Anthony's profile picture
Anthony1 year ago

I do this everywhere it fits. It amazes me that people do not use this pattern more. With the above, you can add 1 line of code to get a hook (vs import React.useContext and the ToastContext). Just use a hook. const {addToast} = useToasts()

Pavel Romanov's profile picture
Pavel Romanov1 year ago

How often do you use context vs libraries like query and zustand in the real world apps?

George Moller's profile picture
George Moller1 year ago

I try to keep the scope of context narrow, otherwise I try to use useState or useQuery as much as possible, haven't been using an outside library for state management for a while now. How about you?

Related Videos