This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-23
Channels
- # announcements (3)
- # babashka (68)
- # beginners (297)
- # calva (13)
- # cider (4)
- # clj-kondo (8)
- # cljs-dev (10)
- # cljsrn (26)
- # clojure (100)
- # clojure-europe (4)
- # clojure-germany (1)
- # clojure-italy (9)
- # clojure-nl (5)
- # clojure-spec (9)
- # clojure-uk (41)
- # clojurescript (69)
- # conjure (70)
- # cursive (44)
- # data-science (20)
- # datascript (2)
- # datomic (55)
- # emacs (1)
- # exercism (3)
- # graalvm (2)
- # kaocha (11)
- # leiningen (6)
- # meander (9)
- # mental-health (1)
- # off-topic (73)
- # pathom (6)
- # pedestal (1)
- # re-frame (3)
- # reagent (52)
- # reitit (8)
- # rum (39)
- # shadow-cljs (152)
- # spacemacs (10)
- # tools-deps (28)
- # xtdb (5)
does anyone know why d/filter applies the predicate function to the unfiltered version of a database? I was banging my head against my keyboard trying to figure out why my filter wasn't returning the results I was expecting until I figured out that the filter was not being applied to the filtered database that I was passing in as an argument, but rather to the underlying original database. It seems like now I'm going to have to cobble together a query on the filtered database and then filter out entities by eid. I'm not a clojure (or coding) expert by any means, but this seems to run somewhat counter to a lot of the patterns I have run into so far in this language where a collection will change through several applications of successive functions.
@d.f.stearns would be easier to say anything with some example 🙂