This is simple and efficient if we know how many subcomponents we are adding. But if we do not want to keep adding these component and want them to get added inside card, then React.Children will be useful. But again, it really depends on what you feel more effective :)
Every time I see/need to build something like this, I think "wouldn't it be great if it was handled by the platform?". In the end, I always opt out for more permissive usage: document correct usage, but don't enforce it in code, just make sure it doesn't blow up if used incorrectly, while notiying the developer about it.
It's a totally valid approach, I'm just complaining on the browser capabilities to write custom components with "children" being handled automatically :)
Like, would be nice if we had not only
<select><optionvalue="1">First</option></select>
But also
<card><header>Title</header></card>
that would handle incorrect children. I know web-components API exist and there are good examples of it, but it's far from being usable for smaller-scale projects.
Lead Frontend Engineer & Certified Neo4j Professional with 8 years of experience. Love to learn and build new things. When not coding, you can find me exploring new tech, games & books.
We can use something simple like this right?
Does using
React.Children.mapprovide any advantage over this code?This is simple and efficient if we know how many subcomponents we are adding. But if we do not want to keep adding these component and want them to get added inside card, then React.Children will be useful. But again, it really depends on what you feel more effective :)
Very nice, thanks. I was facing weird errors but realized I was exporting like
instead of
So make sure to follow the proper syntax. Besides, As @harshdand said, you don't need the React.Children part.
Every time I see/need to build something like this, I think "wouldn't it be great if it was handled by the platform?". In the end, I always opt out for more permissive usage: document correct usage, but don't enforce it in code, just make sure it doesn't blow up if used incorrectly, while notiying the developer about it.
Hey Lex, didn't get what you want to say here. Do you think this is not a good pattern? Will you please elaborate your comment?
It's a totally valid approach, I'm just complaining on the browser capabilities to write custom components with "children" being handled automatically :)
Like, would be nice if we had not only
But also
that would handle incorrect children. I know web-components API exist and there are good examples of it, but it's far from being usable for smaller-scale projects.
True that!
Good stuff!
I only have basic knowledge of React but its interesting to see how you are using
React.Childrenhere.Thanks and keep sharing 👍
Thanks Vaishali. Hope it have helped you in some way.
Not sure if I like this over additional exports. But definitely an concept. Thanks!
Yeah, but try doing it in TypeScript without adding a virtually useless interface 😎
This is interesting !!...Learned something new :)
Thank you! excellent article, just what I was looking for and didn't found
Cool interesting idea.
Make the code less readable, meaningless logic. You can play it like this but you should avoid this.
Thanks for reading the article. Would love to understand why we should avoid this?
thanks for writing this. as a suggestion an example of using the Card component will be useful.