This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-17
Channels
- # architecture (14)
- # aws (4)
- # aws-lambda (2)
- # beginners (66)
- # cider (63)
- # clara (39)
- # cljsjs (4)
- # cljsrn (3)
- # clojure (111)
- # clojure-berlin (5)
- # clojure-italy (17)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-uk (93)
- # clojurescript (19)
- # core-async (60)
- # cursive (13)
- # datomic (22)
- # devcards (2)
- # dirac (4)
- # duct (44)
- # emacs (18)
- # fulcro (1)
- # graphql (10)
- # jobs (13)
- # jobs-discuss (27)
- # lumo (1)
- # mount (1)
- # off-topic (22)
- # om-next (1)
- # onyx (16)
- # philosophy (3)
- # planck (4)
- # precept (34)
- # re-frame (66)
- # reagent (6)
- # ring (2)
- # ring-swagger (1)
- # shadow-cljs (333)
- # specter (8)
- # tools-deps (4)
- # vim (15)
- # yada (1)
hey, i made a new reagent project without figwheel and then tried adding it manually. i hit an issue where figwheel would reload the code but reagent components wouldn’t update, reagent/force-update-all wasn’t helping.
adding a call to reagent/render in reload hook helped probably because (reagent/render [root] (.getElementById js/document "app"))
<- value of root
at page init doesn’t change after figwheel reload
is there a better way to deal with this other than calling reagent/render on reload? is there any cleanup i should be doing, like unmounting or something?
@keymone usually no cleanup is necessary
calling "render" again is the correct way to force a rerender