Quantcast
Channel: Reagent performance issue when passing atom as a function parameter - Stack Overflow
Browsing latest articles
Browse All 4 View Live

Answer by Marko for Reagent performance issue when passing atom as a function...

Looks like the issue here is that reagent doesn't support well components with the controlled inputs due to its async nature.Controlled input (via :value) should be avoided, or worked around by forcing...

View Article


Answer by Dumitru Pletosu for Reagent performance issue when passing atom as...

Both of your versions have an issue. You should use Form-2 type components when using local state. Like this:(defn todo-screen [] (let [value (r/atom nil)] (fn [] [rn/view {:style (styles :container)}...

View Article


Answer by Victor Bjelkholm for Reagent performance issue when passing atom as...

re-frame/dispatch puts your events in a queue for re-frame to process, so there can be a slightly delay before it actually goes through and your change will be there.Sounds like you're experiencing the...

View Article

Reagent performance issue when passing atom as a function parameter

I work on the react-native application using Clojurescript re-frame and reagent. I have one text input component, and have two versions of the code:Version 1: input text is a separate component, and...

View Article
Browsing latest articles
Browse All 4 View Live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>