This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-15
Channels
- # aleph (14)
- # aws (5)
- # beginners (144)
- # bitcoin (1)
- # boot (14)
- # chestnut (13)
- # cljs-dev (58)
- # cljs-experience (1)
- # cljsrn (47)
- # clojure (107)
- # clojure-dev (9)
- # clojure-finland (12)
- # clojure-gamedev (4)
- # clojure-russia (2)
- # clojure-sanfrancisco (1)
- # clojure-spec (5)
- # clojure-uk (28)
- # clojurescript (34)
- # cursive (9)
- # datomic (3)
- # emacs (11)
- # garden (16)
- # graphql (9)
- # hoplon (3)
- # jobs (2)
- # juxt (6)
- # off-topic (32)
- # om (10)
- # onyx (1)
- # pedestal (4)
- # proton (1)
- # re-frame (14)
- # reagent (8)
- # ring (1)
- # ring-swagger (34)
- # shadow-cljs (19)
- # sioux-falls (1)
- # spacemacs (16)
- # testing (14)
has anyone tried saving the om.next/app-state
to local storage so you can load it as the initial state on refresh for offline support?
for some reason it's not really re-initializing, does :normalize false
disable normalization completely?
i mean, it's passing the idents into my components as their state, which is all wrong? oh, and i use om/db->tree in my parser
@cjhowe why aren’t you normalizing?
what i was doing was saving the normalized app state in local storage and trying to use it as initial state, so i tried to set :normalized false
so it wouldn't normalize the (already normalized) initial state. that i guess disables normalization completely, but i do want normalization
for now i denormalize it each time it saves the app state to local storage so it can be used for the initial state, but i'd rather not
@cjhowe ahh, I see. How are you merging to state? AFAIK you can override normalization when merging in if you pass an empty query
(if you’re using om/merge!
or the send cb
)