Right, I meant issue more as something that has to be dealt with rather than Redwood being broken.
I can see this being a typical flow when someone tries to adopt Redwood (at least it was my experience 😅):
1. Start using Redwood with Compose UI
2. Provide a text field implementation with simple mutable state handling like they're used to in Compose UI
3. Scratch their head when the TextField only allows one character to be typed
4. Either give up and assume Redwood is broken (because it works fine in Compose UI) or spend hours debugging until they figure out what's going on
5. Figure out the problem, come up with the solution, implement it
Is the plan to have Redwood provide something like
TextController
/
TextFieldState
and put a disclaimer in the readme that this is how text needs to be handled?
While in practice this might only affect text, in theory couldn't this affect any component where the value is provided from a callback?
