This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-30
Channels
- # bangalore-clj (1)
- # beginners (9)
- # boot (51)
- # cider (20)
- # cljs-dev (419)
- # clojars (1)
- # clojure (338)
- # clojure-brasil (64)
- # clojure-dev (7)
- # clojure-greece (2)
- # clojure-italy (3)
- # clojure-russia (10)
- # clojure-spec (127)
- # clojure-uk (12)
- # clojurebridge (2)
- # clojurescript (132)
- # core-async (8)
- # cursive (37)
- # datomic (34)
- # dirac (5)
- # events (1)
- # funcool (3)
- # hoplon (39)
- # jobs (3)
- # leiningen (3)
- # off-topic (16)
- # om (44)
- # onyx (7)
- # pedestal (20)
- # protorepl (1)
- # random (1)
- # re-frame (64)
- # reagent (6)
- # specter (4)
- # test-check (9)
- # untangled (17)
- # vim (4)
I'm pretty sure I've asked this before but I can't seem to find the answer. Is subselect
the right way to match conditions "deeper" into a tree yet transform higher up?
I realize there's no matching function in this subselect, but still I would have expected found
to be farther up the tree. Instead it's the just the :id which is the last part of the subselect
(s/transform [:data s/ALL #(= "interactor" (:object %)) (s/subselect [:identifier :id])]
(fn [found] (println "FOUND" found))
(:data db))
@rodeorockstar it sounds like you're looking for selected?
but [:identifier :id]
will always match something, maybe you wanted to use [(must :identifier) (must :id)]
?