Clojurians Log v2

true, but if you're in the middle of editing a text input why would you want the value to suddenly change from underneath you?

if there was an exceptional case to be made i would personally probably just keep a ref to the text input and update it as needed instead of keeping the value tied to an atom that constantly updates as the user types. I have witnessed this lag/jank before of doing such a thing and never had to ship code like that before.

> if you're in the middle of editing a text input That's irrelevant. With controlled components, the data drives the UI - exactly what re-frame is made for. Any chance to the app-db, regardless of where it comes from (be it user input or some other event) will update the input. With uncontrolled components, the UI is driving the state, and reversing the direction is quite a hassle. I mean, you do you, but personally I find using uncontrolled components to be drastically inferior.

why not use default-value instead of setting the value directly? I don't think I've ever set an input's :value to an atom

Unless I'm missing something, that would mean that you're using uncontrolled inputs. Meaning, any changes to the data from outside of the inputs will not be registered by the inputs.

None, if you keep its usage to user-controlled inputs.

thanks! that's what i figured. presumably the overall consequence to trying to use it elsewhere is you're just continually bypassing the event queue which is Bad for the obvious reasons, right?

That's my understanding of it, yes.

(See also: this problem has roots in reagent) https://github.com/reagent-project/reagent/blob/master/doc/ControlledInputs.md

Is that really relevant? The re-frame lag is due to how it uses an internal queue - it would work the same exact way regardless of what Reagent uses.

even if you try to wrap the input and create a re-frame-friendly input component, using reagent directly, you will still have issues I took this path, trying to make a wrap to antd/Input, that works as a substitute to re-com/input-text. I ended up giving up 🙂 and styling re-com/input-text to look like an antd component.

Well, yeah - but it will be different issues for different reasons. :) The only common bits are that it's about inputs and async stuff.