This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-23
Channels
- # babashka (68)
- # beginners (133)
- # calva (5)
- # chlorine-clover (21)
- # cider (40)
- # clj-kondo (42)
- # cljs-dev (31)
- # clojure (53)
- # clojure-austin (1)
- # clojure-europe (30)
- # clojure-italy (6)
- # clojure-nl (3)
- # clojure-uk (104)
- # clojurescript (15)
- # datascript (2)
- # datomic (50)
- # emacs (12)
- # fulcro (82)
- # graalvm (4)
- # hoplon (225)
- # jobs (4)
- # jobs-discuss (7)
- # joker (5)
- # juxt (17)
- # kaocha (13)
- # leiningen (16)
- # meander (21)
- # nrepl (18)
- # off-topic (16)
- # pathom (8)
- # pedestal (13)
- # perun (1)
- # re-frame (4)
- # spacemacs (23)
- # testing (28)
- # unrepl (3)
- # vim (5)
- # xtdb (1)
What is the setup for async dynamic resolver? I tried to make an async version of a working dynamic resolver, but the resolver seems to be executed only once and I don't know why
another question: I have this ident query [{[:a/id 1] [:a/x :a/y]}]
against a dynamic resolver. But the first call to the function has env's :dispatch-key
being :a/x
while I expect it to be [:a/id 1]
(meaning: one level up). Is that intended behavior? What's the recommended way to detect such case because I usually infer from :dispatch-key
?
there is a new data point in the reader3
, which is :com.wsscode.pathom.connect.planner/node
(on the env), this contains the planner data about the call, you should look into this instead of :ast
@wilkerlucio is there any util functions to convert an index-io to index-oir? (with a fixed resolver sym, of course)
not possible, they may not match, and have different considerations, so you have to make each differently
consider index-io
is used only for auto-complete (which is important), but things should still work without it
I figured out I'd better stick to pc/add
and have all indexes generated
many thanks