Is it fair to say that <https://github.com/cashapp/redwood/issues/380> is a fundamental issue with R...
e
Is it fair to say that https://github.com/cashapp/redwood/issues/380 is a fundamental issue with Redwood currently (at least with a Compose UI frontend)? A simple fix would be to update
text
directly in the
onValueChange
callback, but that's now explicitly creating multiple sources of truth (which may be better than the current implicit multiple sources of truth, but is still not great). I haven't played around much with Redwood other than with the samples, so I'm not sure if this is an isolated issue with
TextField
because
onValueChange
can be called OOB (because of IME, etc...), or if there are problems with other composables as well. In any case, having to handle it for even just
TextField
seems like a high burden to someone using Redwood.