In principle children in React plays a similar role to slotted elements in DOM templates (Web Components) - but children isn't as powerful as Vue's scoped slots (or Svelte's named slots) which can bind external data into slotted elements.
Under the old terminology both div and a are "ownees" of the owner custom component.
I was trying to point out that custom components don't often use the children prop for elements nested by the owner because of their static nature. Often the component needs to render data into the fragment (much like a template) which requires a "function as child component", a render prop, or injected component.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In principle
childrenin React plays a similar role toslottedelements in DOM templates (Web Components) - butchildrenisn't as powerful as Vue's scoped slots (or Svelte's named slots) which can bind external data into slotted elements.For that purpose renderProps (or component injection) are used in React (example gist).
That might explain why the
childrenprop is so infrequently used in contemporary React.Literally any React element which can have nested elements uses
childrenprop.Just used children two times
auseschildrenfor 'test'divuseschildrenfor the aboveUnder the old terminology both
divandaare "ownees" of the owner custom component.I was trying to point out that custom components don't often use the
childrenprop for elements nested by the owner because of their static nature. Often the component needs to render data into the fragment (much like a template) which requires a "function as child component", a render prop, or injected component.