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
For updating property values, we could either have one message propertyValueChanged(property, newValue?, oldValue?) or have propertyAdded(property, newValue), propertyChanged(property, newValue, oldValue) and propertyRemoved(property, oldValue). Similar for other actions.
Even more generic: featureChanged(feature, oldValue, newValue)
For updating property values, we could either have one message
propertyValueChanged(property, newValue?, oldValue?)
or havepropertyAdded(property, newValue)
,propertyChanged(property, newValue, oldValue)
andpropertyRemoved(property, oldValue)
. Similar for other actions.Even more generic:
featureChanged(feature, oldValue, newValue)
Options for links:
Generic:
changeChild(oldLink?, newLink?, oldParent?, newParent?, oldIndex?, newIndex, child)
Detailed:
addChild(link, newChild, index)
removeChild(link, oldChild | index)
moveChild(link, child, newIndex)
moveChild(oldLink, newLink, oldParent, newParent, oldIndex, newIndex, child)
Option A: generic
Pro:
Con:
changeChild()
has lots of optional parameters in different combinations, need to be figured out in every clientOption B: detailed
Pro:
Con:
Decision: Option B
The text was updated successfully, but these errors were encountered: