Ensure that the framework does not mutate VNode
s and WNode
s
#289
Labels
breaking change
Indicates the issue/pull request would result in a breaking change
enhancement
New feature or request
Enhancement
VNode
andWNode
are decorated with abind
property that holds the instance of the widget that originally returned it from its render. This is problematic as it inadvertently gives access to widget instances by accessing thebind
property, widget instances should not be exposed to end users as instance management is entirely controlled by the framework's vdom renderer.Considerations:
bind
is used to add the DOMNode to the node handler which powers DOM based metasbind
is used to auto bind property functions to the widget instance that created the DNodeThe
WNode
is also modified when a widget registry item is available, with thewidgetConstructor
being updated to reference the registry item.The goal is to ensure that
VNode
s andWNode
s should not be mutated by the framework.The text was updated successfully, but these errors were encountered: