This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-16
Channels
- # beginners (176)
- # boot (11)
- # cider (12)
- # cljs-dev (65)
- # cljsrn (54)
- # clojars (18)
- # clojure (195)
- # clojure-austin (1)
- # clojure-dev (2)
- # clojure-italy (8)
- # clojure-quebec (1)
- # clojure-russia (51)
- # clojure-serbia (3)
- # clojure-spec (24)
- # clojure-uk (28)
- # clojurescript (41)
- # cursive (14)
- # data-science (60)
- # datascript (2)
- # datomic (111)
- # emacs (6)
- # figwheel (1)
- # graphql (16)
- # hoplon (26)
- # juxt (2)
- # lein-figwheel (3)
- # lumo (12)
- # off-topic (8)
- # om (14)
- # pedestal (22)
- # perun (2)
- # proton (1)
- # re-frame (29)
- # reagent (27)
- # ring (17)
- # ring-swagger (2)
- # rum (3)
- # spacemacs (3)
- # unrepl (155)
- # untangled (28)
- # vim (4)
@anmonteiro we default the query to the current route too but do so in a wrapped migrate. I'll make a gist of that to compare with wrapping send.
hrm I suppose that would be a better option, since we wrap migrate anyway
Is there a glossary for om
/`om.next`? I don't see one on the Wiki. It'd be helpful to have clear definitions for concepts like parser
, reconciler
, etc.
@xiongtx https://github.com/awkay/om/wiki/Om-Next-Overview . Found a nice presentation here under "The Pieces of the Mutation Puzzle"
@dnolen remember when you added :easy-reads
? https://github.com/omcljs/om/commit/8ce880dc246f12dbb29c3bfa7fb6563a068f939e
I think the default shouldn鈥檛 be true
just got tripped up on that
that change effectively broke the default behavior
or am I reading it wrong?
@anmonteiro hrm ok, though that鈥檚 an old change now and will probably trip someone else up if we change it
hrm I might be reading the change wrong
I think we preserved the default behavior after all, so there must be something wrong on my end. sorry for the noise