This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-28
Channels
- # adventofcode (2)
- # bangalore-clj (3)
- # beginners (171)
- # boot (28)
- # chestnut (3)
- # cljs-dev (20)
- # cljsjs (5)
- # clojure (280)
- # clojure-austin (1)
- # clojure-czech (1)
- # clojure-dev (9)
- # clojure-dusseldorf (2)
- # clojure-greece (20)
- # clojure-italy (6)
- # clojure-poland (16)
- # clojure-russia (7)
- # clojure-serbia (4)
- # clojure-sg (1)
- # clojure-spec (18)
- # clojure-uk (153)
- # clojurescript (57)
- # core-async (9)
- # cursive (21)
- # data-science (29)
- # datomic (18)
- # dirac (8)
- # docker (6)
- # duct (1)
- # emacs (50)
- # fulcro (15)
- # hoplon (56)
- # klipse (3)
- # leiningen (14)
- # lumo (1)
- # off-topic (5)
- # onyx (13)
- # other-languages (14)
- # pedestal (1)
- # perun (5)
- # planck (17)
- # re-frame (10)
- # reagent (2)
- # ring (1)
- # spacemacs (51)
- # sql (14)
- # test-check (16)
- # testing (1)
- # unrepl (93)
Hello again fellow chestnuts. I'm having a bit of trouble with live reloading. Specifically, project.clj has this line:
:figwheel {:on-jsload "my-app.system/reset"}
my-app.components.ui component to reset, which triggers the core namespace's (render) function to be called, in turn causing re-frame to dispatch the :initialize-db event. The issue is that this clears my entire app-db...say for example that I'm working on some complex workflow, I'm building up app state via the UI, make a code edit, and poof, the app state I've been building up vanishes on system reset.
Is there a way around this? I could sync state to local storage via some kind of interceptor, but that seems heavy handed.yeah, defonce is the way to go for persistent app state
it'd be nice to have a cljs system with the suspendable API to handle things like this, but that's only a wishlist item rn - there isn't anything I've seen that requires more than a defonce yet.