Replies: 1 comment
-
Interesting issue. We don't have the collection changed events in that case. I am curious if INotifyPropertyChanged can be leveraged for this case. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
If I have a
SelectionModel
over nested data, I useChildrenRequested
to get the child nodes of a particular node. Once I return the collection containing the child nodes, theSelectionNode
listens for change notifications on this collection and updates the model accordinglyThe problem comes when the child collection object is replaced on the source data. The
SelectionModel
is unaware of this and there's no way for it to be aware that the child collection has changed.I believe this is a deficit in the design of
SelectionModel
.Steps to reproduce the bug
Place the following in
SelectionModelTests
and run the test:Expected behavior
The
SelectionModel
should have some mechanism to detect a change to the child collection.Version Info
master
(d14b639)Beta Was this translation helpful? Give feedback.
All reactions