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
Component node templates are currently based on nodeComponent property in the dataset. This proposition is to incorporate one or both of the following suggestions:
Node template by slot (#default or #named). This can prevent some prop drilling.
Either solution will work for me, node-component makes a bit more sense to myself
Absolutely, I agree. The reasoning for using slot is to avoid prop-drilling. By having the node component "in the controller", one can manipulate and/or listen to it directly:
Component node templates are currently based on nodeComponent property in the dataset. This proposition is to incorporate one or both of the following suggestions:
Both suggestions are compatible with multiple block types in same collection if neccessary.
The text was updated successfully, but these errors were encountered: