noCascade Incorrect Behaviour (or Documentation)

[thejamespower]

Thanks for your time in creating this lib! :)

According to the docs' for noCascade:

If true, toggling a parent node will not cascade its check state to its children.

This works as expected, however, if you now toggle a child, it does not toggle its parent. If this is the desired behaviour, the docs need to be updated correctly to explain this.

Moreover, for our functional requirements, we need to have this one-way cascade. So when selecting a parent, it does not automatically select a child and when selecting a child it does select all parents in the tree.

Cheers for your help

[jakezatecky]

Thanks for pointing this out.

This was an intended result of that property. The docs should be updated to reflect that noCascade is bi-directional.

As far as your use case is concerned, it may be possible to support that in some future release. I will consider the ease of supporting this.

[kinitkit]

Any updates for this? Thanks.

[neerax]

+1 it would be nice to have separated options for the two behaviours