You need to log in before you can comment on or make changes to this bug.
API from issue 151716 allows addition of subnodes to mobility project, but firing a Change Event doesn't work. The change (adding or removing a node) isn't visible.
Created an attachment (id=89916) [details] Sample code
Please make this work with Tim next week when he's in or office
FYI, I now have a failing test for this problem - looks like the problem actually may be somewhere in Nodes. Should have a fix soon.
The problem is: We are actually using a single key, ChildKind.Foreign, in our Children object, for all nodes from other modules. When a change event is fired, we refresh the keys. But of course, the key list has not really changed - so the underlying Children reuses its existing Nodes, instead of creating new ones. Should be simple enough to fix, just have to decide how.
Fixed in main/ changeset 70a0130084fb, regression tests added
Fix polished further in 951fcbc170fb to use keys from attached NodeLists directly, to avoid briefly clearing the keys of the project node
x
