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
If a user provides an attribute that isn't defined by a component, these attributes should fall through the component and be assigned to the parent of the component. If the component has more than one component as "parents", this is ignored. And if the parent component is a base Manialink tag, the attribute would then end the fallthrough at that point.
This would be useful for a type of attribute inheritance.
If a user provides an attribute that isn't defined by a component, these attributes should fall through the component and be assigned to the parent of the component. If the component has more than one component as "parents", this is ignored. And if the parent component is a base Manialink tag, the attribute would then end the fallthrough at that point.
This would be useful for a type of attribute inheritance.
For example, given the following component code:
Let's call this component
HelloLabel
Currently, there is no way to directly set any attributes to the
<label>
without explicitly defining properties.But with fallthrough attributes it can work like this:
The attribute
textcolor
would then fall through and be assigned to<label>
. So the result would be:This fallthrough would also go recursively, and fall through multiple components until a base manialink tag is hit.
Now imagine the
HelloLabel
had two parent tags:In this case, it makes the fallthrough attribute ambiguous, and will be ignored.
The text was updated successfully, but these errors were encountered: