RookY2K

> Aah. I can see how this one might become a challenge for RDS. I would assume some internals only consider flat array and not nested with children. I will...

Also, just to be doubly certain, I removed the `children` attribute from `A` and just hard-coded some of the utility functions with the correct parent / child relationships. So RDS...

Based on the ordering of the console logs, here is what I _think_ is happening: 1. De-selecting `A` causes two things to happen within the same update cycle: 1. `A`...

Here is the simplified codesandbox that more succinctly demonstrates the issue: https://codesandbox.io/s/rds-onchange-issue-ri5zyo The basic setup is that in the `handleChange` callback definition, I add the third option to the updated...

> Here are several different options selected with one hit. 1st, 2nd and 4th The issue isn't with selecting multiple options at one time. The issue is updating the `values`...

To be clear, this _is_ a bug. RDS _should_ be able to handle `onChange` updating the `values` prop. It cannot due to the code block I highlighted above. Here is...

For the record, I've already developed a workaround to have everything update as expected for my use case. I just wanted to make sure that the bug was brought to...

Also, to be clear, this is _not_ an internal react issue. Due to how RDS works, clicking an option updates `values` in state. It isn't until that state update has...

> Bug on RDS or not, I never said it was an issue on react, I think it is prevention of loop. I might be wrong. But updating state and...