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
The current API for node events involves setting a callback as a property of the node. This forces consumers to compete for access to the property namespace, risking inadvertent overwrites or insufficient patching, which can disrupt existing closures. To address this, the node (and widget) events API should be enhanced to use a more reliable pattern such as events/listeners.
In particular, this improvement would improve the ability to register listeners to node lifecycle events, which is becoming increasingly important as the number of scenarios has increased in which objects tied to a node's lifecycle aren't automatically garbage-collected upon node removal—for example, Vue components, floating DOM elements, or Pinia store items keyed to the node.
The text was updated successfully, but these errors were encountered:
The current API for node events involves setting a callback as a property of the node. This forces consumers to compete for access to the property namespace, risking inadvertent overwrites or insufficient patching, which can disrupt existing closures. To address this, the node (and widget) events API should be enhanced to use a more reliable pattern such as events/listeners.
In particular, this improvement would improve the ability to register listeners to node lifecycle events, which is becoming increasingly important as the number of scenarios has increased in which objects tied to a node's lifecycle aren't automatically garbage-collected upon node removal—for example, Vue components, floating DOM elements, or Pinia store items keyed to the node.
The text was updated successfully, but these errors were encountered: