Should we invoke onStateChange with _all_ the state? about downshift

[the-simian]

I would prefer that, myself. I noticed in the function that you passed most of what I'd be looking for, but why not show it all? Someone therefore can fire a side effect of any mutation they need at this point, and you're allowing folks to access the plumbing more easily.

Ultimately the big picture for this project seems to be that it is an api that enables folks to build any ui, so exposing more is not out of touch with the design direction of the component.

[kentcdodds]

It's published as the latest rc 😄

[kentcdodds]

Cool! I've almost got that done. Thanks for the validation.

Also, I'm improving things slightly. So now your onStateChange will only ever be called when state actually changes (not when setState is called) and it's only called with the actual changes (in addition to the second parameter which includes all the state). I think that's what we always wanted, but it wasn't doing that. So I guess you could call this a bug fix 😅

[the-simian]

Ok I'll update my examples with this in mind, I plan on adding more features to it when this version is published also.