This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-27
Channels
- # announcements (2)
- # aws (17)
- # babashka (13)
- # beginners (84)
- # calva (46)
- # chlorine-clover (40)
- # cider (19)
- # clojure (27)
- # clojure-australia (1)
- # clojure-europe (84)
- # clojure-nl (2)
- # clojure-uk (49)
- # clojurescript (65)
- # core-async (6)
- # cryogen (1)
- # cursive (11)
- # datomic (13)
- # etaoin (3)
- # jackdaw (5)
- # jobs (2)
- # kaocha (34)
- # minimallist (6)
- # off-topic (17)
- # pathom (2)
- # pedestal (11)
- # re-frame (8)
- # reagent (5)
- # rewrite-clj (19)
- # shadow-cljs (30)
In a simple reagent component using let
and a local r/atom for state, what causes the component to re-render? I can’t figure out why 2 similar forms are behaving differently in this regard.
One component is working fine, the other ‘on change’ is triggering the component to re-render as if the incoming data has changed, but from what I can see, only the local r/atom should be updating with each edit.
It’s too unwieldy, but I appreciate the offer. I found wrapping the hiccup in a fn
and returning that seems to have solved the issue, though. Not sure why the already working component did not need that approach.