This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-25
Channels
- # announcements (8)
- # babashka (58)
- # beginners (59)
- # biff (4)
- # calva (39)
- # cider (2)
- # clj-kondo (8)
- # clj-together (4)
- # cljdoc (5)
- # cljsrn (1)
- # clojure (60)
- # clojure-australia (2)
- # clojure-europe (16)
- # clojure-nl (1)
- # clojure-norway (3)
- # clojurescript (13)
- # conjure (10)
- # cursive (9)
- # datomic (5)
- # dev-tooling (1)
- # emacs (6)
- # events (1)
- # graalvm (38)
- # graphql (5)
- # joyride (1)
- # kaocha (3)
- # lsp (23)
- # malli (2)
- # mount (2)
- # off-topic (31)
- # other-languages (13)
- # pathom (3)
- # polylith (12)
- # portal (4)
- # practicalli (22)
- # re-frame (6)
- # reagent (3)
- # releases (3)
- # sql (4)
- # squint (3)
- # tools-build (10)
- # tools-deps (10)
- # xtdb (4)
[RESOLVED] Hi o/ I am trying to see which attributes a node is trying to resolve, I've thought that I could rely on ::pcp/source-for-attrs
which is used at https://github.com/wilkerlucio/pathom3/blob/main/src/main/com/wsscode/pathom3/connect/runner/stats.cljc#L72, but I don't see it in my run-stats response for a query (see below for an example).
Is this expected? Maybe is there another way to see the current attribute a node is trying to resolve?
{... ...
:com.wsscode.pathom3.connect.planner/nodes
{20
{:com.wsscode.pathom3.connect.operation/op-name my.resolver/a->b
:com.wsscode.pathom3.connect.planner/expects #:db-my.person{:id {}}
:com.wsscode.pathom3.connect.planner/input #:my.person{:external-id {}}
:com.wsscode.pathom3.connect.planner/node-id 20
:com.wsscode.pathom3.connect.planner/node-parents #{21}
:com.wsscode.pathom3.connect.planner/run-next 16},
... ...}}
the attributes a node is trying to resolve are in :com.wsscode.pathom3.connect.planner/expects so in your case #:db-my.person{:id {}}
Hunnnn, I’ve thought this was the return of the resolver, but you are right, Eric! Thanks :D Wonder if source-for-attrs is really used anymore