Un-Suck Your React Components - Composable & Compound Components
ฝัง
- เผยแพร่เมื่อ 25 มิ.ย. 2024
- Learn how to apply component composition to solve prop-drilling and make your components more flexible. Take your components to the next level by using the context API and building Compound Components.
🏁 Final code: stackblitz.com/edit/react-ts-...
🌟 Subscribe to my channel and FINALLY learn to build more than just a to-do list with React: / @vincasstonys
Here's the platform I recommend to learn Web Development online: www.educative.io/explore?aff=...
For more content:
- Follow me on Twitter / vincasstonys
- Read my blog at codefrontend.com
0:00 Intro
0:56 Problem Explanation
2:01 Component Composition
7:20 Adding the Context API
12:56 Compound Components
15:45 Outro
Tech used in this tutorial:
- HTML / CSS
- React.JS
- TypeScript - วิทยาศาสตร์และเทคโนโลยี
Sorry for the gaps from 4:56 to 5:00 and 5:05 to 5:09, editing fail, will try to double check better in the future 🤦♂
No worries! Very well done video. Very informative. There's a lot of beginner content on TH-cam but not as much architectural content, so I really appreciate you sharing your take on the subject. Just subscribed! Looking forward to more of this kind of content 😁
You realise you can cut the gaps out in the TH-cam creators studio without any need to reupload, don't you?
So I'll just ... children. 😁
I've been using the compound component pattern for a while and this is a great visual explanation of the benefits and how it's implemented.
The pattern is a good example for Separation of Concerns / SOLID principles - Single responsibility, Open-Close, Dependency inversion.
I like how you always type 'Node' as 'NOde' haha
What a great way to group components and their relevant data. I've been using React in production for nearly a year now and it never occurred to me to use a Context at this deep level before.
Really good video, thanks for sharing!
Same here, using Context at deep level sounds like a nice idea. But as many others have pointed out, it comes with its own challenges of tightly coupled component that could have been mistaken for "NOT TO BE REUSED AT OTHER PLACES".
This looks like a very fun pattern to use. At first I was not sold on the whole namespace thing with Component.Name but it grew on me.
This code looks so clean! I love refactoring code videos
That's exactly what I've been looking for!
Thank you man! Please don't stop posting videos, I'd rather watch your tutorials than netflix
Really clean video, showed the process really well. I think the really great thing about this approach is that you can easily create variants. It is really good if you need to use the same code base to support multiple clients for example.
Man keep these types of videos coming and you will be one of the top TS/React youtubers in no time. I would like to ask for the next videos if you could dive deeper into the pros or cons. Thanks and best of luck! :)
Very nice! I never thought of using the context API like this, this is super useful, thanks!
Awesome, glad it was useful 👌
This video has insane value. I'm working on my own web app, and this concept, when well applied and in the right situation, is a game-changer. The code without it, turns out to be simply a mess, but when applied properly, it provides the exact modularity needed. Awesome!
Really great concept that can actually be applied to almost any front-end framework that's out there today, thanks for sharing!
10 seconds in and I’d already subscribed! Really liked this tutorial, looking forward to your future content. TH-cam needs a lot more React design pattern videos like this.
Thank you for making this video. I like how you explain this concept. It's easy to understand.
Great video, Vincas. Thank you.
Man I was Just Thinking about the Same Problem for Scalable Components" and The TH-cam Recommended it to me. I am Happy now😊😊
Hey Vincas, I just wanted to let you know that this was a masterful lecture, and really informed my coding style! I'll be writing a small storybook component library for my startup this week and your patterns have really shaped the approach I wanna take. So thank you for providing such high-quality instruction!
Secondly, I just wanna point out for anyone that uses NextJS *13* that context is a client side feature, and will not work without the "use client" directive at the top of the file. This also means that if you want to fetch data server side, say in an async function, you will probably need to have a state initializer component that can interface between the server and client. Jack Herrington (author of No BS TS -- and he has a TH-cam channel under his name) has a video going over state management in NextJS 13 to cover this topic.
Again, Vincas, I really appreciate this! Thanks, and greetings from the US 👋🏽 Subbed.
Thank you! You should also take a look at Radix to see how a similar approach is used in practice.
you content is perfect to level up. i hope you dont stop
👏👏more content like that!
Great explanation
That was eyeopening. Thank you!
I literally faced this problem on a project i am working on right now. Thank you!
This video is amazing. I learned so much from this!! Keep making content like this
This is such a fun and informative video. Love it!
This is a very precious video! Thanks a lot!
Exactly what i'm looking for. Thank you 👍
FINALLY. I needed to know how headlessUI makes their components thanks ALOT
That was awesome. Thanks!
Very good and thorough step by step.
I really enjoyed it. Keep it up 👍
This is great, never thought of doing it this way.
Great video. Not 100% sold on it all being a best practice, but really useful for everyone to understand how it works
love this video. i learnt soemthing new and had to come back to it just to see what i missed.
Great Tutorial, Thanks for sharing this awesome tutorial.
That's an amazing explanation for me, thanks a lot!.
danggg it! I've seen this pattern started from headless-ui a couple years ago and nowadays as my experience increases, I see a lot more, the most recent is radix-ui which I (we) love hahaha
I try to learn this kind of approach back then from headless-ui, sadly I understand nothing, lol. A couple years later, I try to learn again from headless-ui and radix-ui, then your video showed up at the very right time.
thank you for making a very clear tutorial and a good example whereas this kind of card can be very complex at some point. I really enjoy watchin this video a couple of times.
Thanks! 🙌
Great Content!!! Keep doing this!
Thanks!
Thanks so much, never leave comments but this is such a good tutorial 🔥🔥🔥
Dam I learned a lot from this tutorial keep them comming
Great one mate 🙌
You did great, a lot of good knowledge from you. Thank u so much.
this type of react content is lacking on youtube. Make some more my man!
A very good and informative video Vincas, thanks for this 🙇♀🙇
Sam Selikoff has a great set of videos on implementing RadixUI components which follow a similar design. In fact, once I saw the end result of using the Context API to make the components modular I couldn’t help but think I had seen it somewhere before.
It was a great video and I learned a lot! Subbed 😊
This is a great video!
Subscribed!
Bro you saved my ass trying to bootstrap a reusable pattern for my library 🙏🏿 thank you
Wow. Very helpful.
got to know something new ,thanks a lot
great explaination, loved it
Thanks, I appreciate the kind words!
Awesome video, keep it up 👍
Dood! This is fantastic, I just did something like this and I wish I had seen this first, because you made it easy
Thanks, I'm glad it was helpful!
One of the best 👌
Bro, what a great content, keep it up, that's very helpful. I'm already writing a tweet to share it! Thank you!!
Nice video! I like the demonstration of Component Composition and also the "name-spacing", however, I wouldn't agree with the use of Context API here: Firstly, in the first part of the video you show how to make the component more reusable with Component Composition, but then with the Context API you introduce maximum-tight coupling to the Context, which arguably impedes the reusability. Secondly, in a way, I'm thinking Context API is just "hidden" prop drilling where the dependency isn't visible at first sight, which might not be ideal in terms of readability for other developers.
True, this and hidden data flows are the reason I tend to avoid the Context API.
Correct, also gosh !! if anyone is using vanilla js with react good luck accessing/handling those product attributes after change in product's attributes.
Agreed, I'm definitely going to apply the idea about Component Composition, but the rest of the video sounds like it's better for demo projects to look as "clean" as possible rather than for real-world code. I'm more likely to use , and and other similar lower-level components as children rather than , and . It's a lot more flexible and it's still very readable.
Context helps those composition components which are grouped and enter linked like Select & Option.
great video with great quality . I love it .
Thank you! 🙏
awesome tutorial. Keep em comig
you are the best one explain compound component
Great content!
I can only like this video once unfortunately... Really brilliant explanation and example, well done :)
great video !!
Wow, amazing.
Loved this video♥. Instant Subscribe
Lovely content
Holly shit this is nice! Thanks for sharing!
This is amazing
I myself, prefer to develop components so they're easier to use consumer side, I feel like providing variations of a component as a prop is much easier, pass through an Id for the product, and have all logic relating to fetching and deciding layout to the component, learning curve for other developers is much nicer, and you're using the same composition in every place, it makes it much harder to fix bugs or make changes, where if it's inside the component, maintenance is much easier, you end up having to create wrapper components too many times with composition too so that things are reusable
I wish I saw your video earlier. I just had a live coding interview and had no idea about this principle...
very good video, you opened eyes :D Got a sub
Wow thank you
Considering info & action prop as childrens would make this more clean and easy to understand
wow, I learned a lot
amazing content
thanks i love it
I see this composition pattern in the MUI implementation, personally I think this may suite for base components with infrequently change structure. Suppose your Card component need modifying to grid style, it's hard to maintain both `slot` styles and props-components styles.
Another problem is manage reference of slot props, which can lead to performance issues, but if you using old class component with some properties like `renderImage`, `renderRating`, etc, this is a good way to simplify your component.
I'm just learning React but wouldn't memo solve those performance concerns you talked about?
@@davien001 Yes it would, but at the same time you will have to maintain multiple memos instead of having a single memoization step for the entire component.
Very good content! As some people already pointed below, you need to work on the editing. I know it is hard, but this type of things helps to understand better your content.
Absolutely agreed, I'm trying to get better with every video. Do you have suggestions in mind for what I should work on?
@@codevincas I noticed one black screen during the video (4:56). The rest is already pointed by @the stunning iitian.
@@Mong3 Indeed, good point, I totally missed the blank section, sorry about that 😅
nice 🔥
i really dislike this sort of composition. i call it fake composition. the internal components are just a longer way of specifying props (as opposed rendering something).
- components become 10X more complex because of the need to maintain a context and everything around it.
- zero type safety. which components are allowed inside? is the order important? how about nesting?
- because of the type safety thing, you need to maintain docs for the thing. instead of just asking TS to let you know which props it accepts.
What is the real composition?
This comment is underrated. You also turned each of these components required to be used within a context. Instead of using props, makes the sole use of the component to be within the product card component. It its also very hard to test, as you need to mock a context in order to be able to test the components instead of simple passing props to the components youre testing.
Props > context api.
This is simply over engineered
@@ChristianMoentest Valid point, and I do not advice using this pattern everywhere. It's very helpful for building design systems, especially public libraries as this prevents unintended usage and simplifies the API for the user. The testing is indeed a bit harder, though I don't see much point in testing the sub-components individually as small and simple as they usually are.
@@codevincas So for me, a real composition would be something like Settings. If the internal components are just a fancy way to set props it's just an over complicated configuration method IMO.
1. How do they become more complex? You create a context and wrap a Root component around the Provider. You can create all your components in a single file-is it really that hard to maintain a scoped context?
2. Why does it matter which components are allowed? Order shouldn't be important. You're creating arbitrary restrictions that makes it harder to reuse for other cases. You're making up an API which takes _more_ effort to implement than just accepting any component. If your intent is to map over the children to stuff props onto them or filter out, then don't. That's what compound components solve for you.
Compound components makes decisions easier at the consumer level, rather than implementation level, making them great for reusability.
3. I don't get this. The compound component is just a component built up of other components, whether it provides a context or not. Each component defines their own props.
That said, this is by no means a recommendation that you should make everything a compound component. It's still more effort than just making a special-case component that does what it needs. However, they are a great abstraction when you want more flexibility without imposing restrictions and unnecessary implementation details.
Thank you
gražiai padarytas video. Užprenumeruosiu, reikia palaikyt :D. Nors pats React nelabai naudoju, bet principai visur panašūs, tai vis tiek naudinga.
Nice pattern
ReactNOde 3 times in a row, bingo!
Great video lol it makes me want to refactor my whole codebase
Glad you enjoyed, but don't refactor unless you absolutely need to.
Thank you for the video. You can achieve namespacing by perhaps importing everything on a separate file as non default exports if the issue at hand is too many lines of imports. I will personally always favour to as on the latter you're creating a data dependency where the first one you can easily erase Product and will still exist. You could then import everything in one line.
Very nice
Super nice, thank you for this! By the way, any way to do this with React Server Components without having to use ‘use client’?
Amazing video.. Keep it up. 👍
Thank you! Anything you would like to see me cover?
@@codevincas I think, You could make a video on code optimization in React app.
Interesting. It reminds me the way I used to work with slots in Vue js.
nice code, but how is the performance if you have a lot of card (contexts)?
Hi! Excelent video, but I have a question, React recommends to use Component Composition every time it's possible and avoid (as much as you can) the use of ContextAPI (Re rendering problems). Will you use Context in a real app in the way you are showing right now? Thanks.
there are quite a few draw backs from using this. But for some cases this is quite useful.
Could you provide some of the draw backs please?
@@xacxdcx for starters it’s got no lateral reusability
Great video! I can't to help but to ask why do you think this is a good approach? When in fact we can make the component accept one prop, and object with all the data necessary to render the component.
You could, and for most components that's totally acceptable, and anything more would be overengineering. As I mentioned in the beginning of the video - what happens when you want to slightly change the appearance of the component, for instance hide some parts of it or add a small bit of logic? You'd add boolean flags and change the component implementation logic to accommodate for them. That's fine while there aren't that many flags - most components never reach that point, so that's ok. But particularly design system components are often used in multiple different ways with slight tweaks for each use case. In that case changing the implementation of the component becomes risky and cumbersome, also the component's implementation logic would grow to support all those different use cases and the prop list would be mostly a bunch of boolean flags. Just passing in an object doesn't help in that case, because it doesn't change the need for those flags and in many cases design system components won't even be using a domain model (the object), but rather generic props to retain flexibility. In that case, composable components are superior. If you want to use the context and compound components - that's your decision, in many cases it would be over-engineering, but in some, they're a nice way to group components together.
So this is svelte slots in react? Pretty cool
Hey,, excellent video! Just a quick question. Let's imagine that you have to render 100 ProductCards. In that case, would you create 100 Context for each card? Thanks!
This is a great pattern but could easily be broken by other engineers who didn't know what components to pass on the slots, which can be solved by strictly typing, this has pros and cons
How about performance when many compound components are defined?
So you need to create a context for each of your main components, isn't this going to impact your performance and readability ?
They're all using the same context. I don't recommend using this pattern everywhere, only when flexibility that it gives you is actually benefitial.
@@dealloc then you might as well stick to props drilling or use redux/recoil
@Code With Vincas Yes, I know they are, but now you want to create something completely different, and to keep the design pattern consistent, you need to make a new context for this completely different component.
In which it makes it a bit more complicated and increases the difficulty of readability
Nice tutorial, though 👌
This looks like combining the "Render Prop" pattern with "Compound Components."
Let's see if I understood correctly the right use cases of this:
I should/could use this whenever I have a component that needs some more details, but those details alone wouldn't be something that I could reuse elsewhere
Seems like this, am I right? :)
Hey Vincas, can you add the initial code in a repo and share it here, It will benefit some of us who want to follow and code alongside.
What are the memory and performance implication for using so many context though if we are replicating it multiple times?
cool😎
Very clear explanation, thank you