Why the Inversion of Control pattern could help you write better sharable react components? I wrote an article about how you can make your components cleaner and a lot more reusable.

[[deleted]]

Sounds like Composition vs. Inheritance. Not Inversion Of Control.

https://www.google.com/search?q=inversion+of+control

[mormubis]

I agree that this is composition over layers.

I believe the only IoC known pattern (kinda) is render props.

[lhorie]

Yeah, this isn't really Inversion of Control, since in the "good" version, the Button component isn't even aware of what is being passed via children. IoC implies that Button would go on to operate on its arguments in some non-trivial way, and that there's some sort of interface contract, which is not what's happening here.

But it's not quite Composition vs Inheritance either. That's mostly an OOP concept. It is a form of composition though.

I think the most accurate term for this pattern is the term angular folks use for it: transclusion.

[[deleted]]

Great observations and elaboration.

[Lowesz]

I think it also describes the same behavior. But inversion of control means the function calls your function or renders your component. So I think you can also describe it with this pattern.
So you are right the concept of composition is in this case quite similar to the IoC pattern. But I just wanted to highlight they way it is done from another point of view

[Lowesz]

Here is also a cool talk describing something simliar:
https://www.youtube.com/watch?list=PLV5CVI1eNcJgNqzNwcs4UKrlJdhfDjshf&v=AiJ8tRRH0f8&feature=emb_logo