Been thinking a lot about component composition and how overlook this "feature" is in most codebases.
Reacr is ineheretrly composable one can argue that composition is the whole point of React and the component model.
So, why is not used more frequently?
Reacr is ineheretrly composable one can argue that composition is the whole point of React and the component model.
So, why is not used more frequently?
One reason could be that: is not the default mental model.
Is like the default way we structure components in our minds is just inheritance. Containers containing more containers.
This approach of will definitely ends up in a prop drilling issue at some point.
Is like the default way we structure components in our minds is just inheritance. Containers containing more containers.
This approach of will definitely ends up in a prop drilling issue at some point.
But. What is prop drilling and why is an issue?
Prop drilling is a "feature" or at least capability of components to share data between them.
Props are the way components communicate each other. Is their API, and through this, you can pass data from a parent component.
Prop drilling is a "feature" or at least capability of components to share data between them.
Props are the way components communicate each other. Is their API, and through this, you can pass data from a parent component.
Therefore prop drilling is the main technique to share data across components from parent to children. But why is considered an issue? Because at some point the component tree is so nested that passing props down is a pain since the data is required deep down in the tree.
This is when we should reach to composition. Most of this component usually are just "layout" thing instead of logic containers so they are just acting as proxies of the data passing it down to the next children.
@mjackson have a very good tal about this.
@mjackson have a very good tal about this.
So if is so nice why is not used more often? I think is just old behaviors that stick with us.
Proop drilling is often related with state management and was a big buzz word when Flux came into play and later Redux. (Old days).
Then we saw a solution tight there.
Proop drilling is often related with state management and was a big buzz word when Flux came into play and later Redux. (Old days).
Then we saw a solution tight there.
We started using Flux alike implementations moving everything outside of React tree trying to avoid prop drilling and hoping to replicate this model of Component as function of state. But we completely forgot of composition.
Later one Context became the norm and we still doing the same as before. Moving all of the shared data into one global store to share it across.
So, even tho Context is awesome IMHO is a very good tool for library authors but for app developers we should use composition more often and at same time do lote to make it a known concept.
If sounds interesting please RT the first tweet 👍👍
https://twitter.com/matiasfha/status/1395009961206427659?s=21
• • •
Missing some Tweet in this thread? You can try to
force a refresh
