This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-10
Channels
- # announcements (4)
- # beginners (111)
- # boot (34)
- # cider (67)
- # cljdoc (10)
- # clojure (90)
- # clojure-dev (37)
- # clojure-europe (3)
- # clojure-gamedev (3)
- # clojure-italy (18)
- # clojure-losangeles (2)
- # clojure-nl (27)
- # clojure-spec (24)
- # clojure-uk (59)
- # clojurescript (41)
- # cursive (32)
- # datomic (31)
- # emacs (21)
- # figwheel (1)
- # figwheel-main (2)
- # fulcro (43)
- # graalvm (6)
- # graphql (3)
- # jobs-discuss (3)
- # kaocha (1)
- # nyc (1)
- # off-topic (22)
- # pathom (10)
- # pedestal (11)
- # re-frame (9)
- # reitit (17)
- # shadow-cljs (15)
- # spacemacs (13)
- # sql (6)
- # testing (5)
- # tools-deps (3)
- # vim (13)
- # yada (1)
@souenzzo what "in anger" means?
A resolver should ALWAYS return everything that it's know? Can I consider it a bug? https://gist.github.com/souenzzo/c120fdc37311341bffd97036ec339766
@souenzzo no, it doesn't have to, the issue you see is because of caching
the first call will cache the result, and since from the first to the second the input didn't changed it will hit the cache
you can set ::pc/cache? false
(in the resolver config) to disable it, but then you need to manual cache yourself if you want avoid multiple calls to the same resolver
👍 4