This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-11
Channels
- # aleph (5)
- # beginners (13)
- # boot (2)
- # cljs-dev (1)
- # clojure (12)
- # clojure-italy (1)
- # clojure-russia (67)
- # clojure-uk (2)
- # clojurescript (49)
- # datomic (1)
- # defnpodcast (3)
- # graphql (8)
- # jobs (1)
- # lein-figwheel (1)
- # leiningen (1)
- # lumo (9)
- # off-topic (5)
- # om (3)
- # parinfer (13)
- # pedestal (2)
- # re-frame (5)
- # reagent (4)
- # ring-swagger (2)
- # untangled (13)
- # yada (2)
bbktsk: I don't see anything wrong with that. I'm not sure you need to call the parser recursively though. You probably wouldn't have a read function for person/id person/firstname, etc, unless you're fetching all these values from very disparate sources
if there is an invalid ident (i.e. non existent) in app state, when using recursive query I get Error: ... is not ISeqable
from the db->tree
- for some reason I thought it would just be ignored (as when querying other inexistent keys). Example:
(let [st {:tree [{:id 1 :children [ [:by-id 2]]}]}]
(om/db->tree
'[{:tree [:id {:children ...}]}] st st))