You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be some overlap between children / slots, both appear to do similar things via different api's. Are there plans to allow a defaultValue to be defined for either/both of these? It would be really useful to either be able to point to an arbitrary value (ie - string) or another already defined component with some set props.
The text was updated successfully, but these errors were encountered:
Hey @samiresua - apologies for the delayed response to your question.
I would describe children vs slots as this:
children is useful for nesting elements into the same container. (more common)
slots are useful for creating multiple containers for nesting elements in different areas of the component. (allows for additional flexibility to create more complex layouts within a single component)
You are right that currently both children and slots do not accept default values. I will bring this idea to the team for discussion and will let you know. Thanks!
There seems to be some overlap between children / slots, both appear to do similar things via different api's. Are there plans to allow a defaultValue to be defined for either/both of these? It would be really useful to either be able to point to an arbitrary value (ie - string) or another already defined component with some set props.
The text was updated successfully, but these errors were encountered: