fulcro

Mark Wardle 2026-02-03T15:29:51.018409Z

Just tidying up prior to a release, and updated a fair number of dependencies including React and Fulcro. Now I'm getting 'Warning: A component is changing a controlled input to be uncontrolled. This is likely caused by the value changing from a defined to undefined, which should not happen. Decide between using a controlled or uncontrolled input element for the lifetime of the component. More info: Error Component Stack' from all of my textfields on first use. It's more of an annoyance rather than having any problematic functional consequences. I'm on Fulcro 3.9.1 now, React 18.3.1. I can do some work to go back versions if this might help.

tony.kay 2026-02-03T20:03:37.677639Z

So, I’m not aware of any regression there. You’ve always needed to make sure you have your values non-nil (e.g. (input {:value (or v "")} ) to avoid that. Are you saying that now you’re seeing nils (even momentarily) where you didn’t before? Could be a change in performance is causing a render before something else you’re doing…my general advice is to review you inputs and make sure the value is never nil, even for brief interstitial renders)

Mark Wardle 2026-02-03T20:10:04.074129Z

Thanks Tony. I'll double check as I thought I have that sorted.