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
Currently if one wants to use a tag in a nested component, the tag needs to be redeclared in every level. This is not only unergonomic, but also leads to the tag defining its (meaningful) attributes at the first level.
Take the following example. Ideally we would like to define the constraints for the #Tree in the "MainNavigation" component.
Currently this is not possible, because the implementor (CMS) is asked for the data at the top level (PageDefault).
A solution would be to add a syntax for letting a tag "fall through". This way the tag could be defined where its actually used and it would not need to be redefined at every level.
In this case the #text on the button would reuse the data of the multiline text defined in the "MediaText" component.
This needs a solution, which could be that the user can define a new key for the redefined tag.
A syntax could look like this:
Currently if one wants to use a tag in a nested component, the tag needs to be redeclared in every level. This is not only unergonomic, but also leads to the tag defining its (meaningful) attributes at the first level.
Take the following example. Ideally we would like to define the constraints for the
#Tree
in the "MainNavigation" component.Currently this is not possible, because the implementor (CMS) is asked for the data at the top level (PageDefault).
A solution would be to add a syntax for letting a tag "fall through". This way the tag could be defined where its actually used and it would not need to be redefined at every level.
This could look something like that:
The text was updated successfully, but these errors were encountered: