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 an element wishes to communicate with another element it issues a 'global' action (starts with '.', which will hit the first ancestor element in the ancestors chain that has an update for this action defined.
same as thread except that the action is attempted on each element defined in the selector until a recipient is found in which case the threading stops
deprecate "global" actions (starting with a .)
reimplement "global" actions using threadToFirst
The text was updated successfully, but these errors were encountered:
Currently, if an element wishes to communicate with another element it issues a 'global' action (starts with '.', which will hit the first ancestor element in the ancestors chain that has an update for this action defined.
Introduce new way of threading actions.
elUpdates.thread(action, movementOrSelector, targetAction)
movementOrSelector
parameter can bezip.select
) which can be used to select one or more elements (starting from the current element's location)targetAction
is the the action to be triggered on each of the target elements. It is optional, and if not provided it is the same asaction
elUpdates.threadToFirst(action, selector, targetAction)
thread
except that the action is attempted on each element defined in the selector until a recipient is found in which case the threading stops.
)threadToFirst
The text was updated successfully, but these errors were encountered: