This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-10
Channels
- # aleph (2)
- # arachne (1)
- # beginners (5)
- # boot (33)
- # cider (12)
- # cljs-dev (6)
- # cljsrn (26)
- # clojure (33)
- # clojure-austin (7)
- # clojure-belgium (6)
- # clojure-chicago (1)
- # clojure-dusseldorf (1)
- # clojure-fr (1)
- # clojure-hamburg (1)
- # clojure-nl (11)
- # clojure-portugal (3)
- # clojure-russia (14)
- # clojure-spec (35)
- # clojure-uk (28)
- # clojurescript (49)
- # component (7)
- # core-async (75)
- # cursive (13)
- # datomic (15)
- # dirac (57)
- # emacs (5)
- # events (1)
- # hoplon (34)
- # jobs (2)
- # jobs-discuss (8)
- # lambdaisland (1)
- # lein-figwheel (7)
- # leiningen (3)
- # om (5)
- # onyx (8)
- # re-frame (56)
- # reagent (13)
- # testing (7)
- # untangled (30)
- # vim (51)
- # yada (17)
thanks for that, reading this page was very enlightening
I need a library for manage routes management. I’ve seen Secretary
and Bidi
. What do you think is better?
Hmm, any hints why after re-reading keys :ast doesn’t have :query anymore?
(om/transact! reconciler ‘[:board/list])
[..logs] ast {:type :prop, :dispatch-key :board/list, :key [:board/list]}
Essentially sends empty route to the back-end.. Can’t quite figure it out.As opposed to initial rendering, (say on page reload)
ast {:type :join, :dispatch-key :board/list, :key :board/list, :query [:db/id :board/name :board/description], :component boards-io.components/BoardItem, :children [{:type :prop, :dispatch-key :db/id, :key :db/id} {:type :prop, :dispatch-key :board/name, :key :board/name} {:type :prop, :dispatch-key :board/description, :key :board/description}]}