This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-20
Channels
- # announcements (1)
- # asami (19)
- # beginners (6)
- # biff (1)
- # cljs-dev (3)
- # clojure (27)
- # clojure-europe (7)
- # clojure-gamedev (4)
- # clojure-hungary (47)
- # clojure-nl (5)
- # clojure-norway (29)
- # clojure-uk (5)
- # clojurescript (23)
- # data-science (1)
- # emacs (36)
- # events (3)
- # fulcro (22)
- # graphql (1)
- # gratitude (1)
- # introduce-yourself (3)
- # lsp (5)
- # nbb (7)
- # off-topic (68)
- # other-languages (2)
- # pathom (5)
- # reagent (4)
- # reitit (10)
- # remote-jobs (2)
- # reveal (2)
- # ring (1)
- # shadow-cljs (46)
- # spacemacs (15)
- # tools-deps (4)
In Pathom 3, is there a reason why I would be able to write a nested query, but when I write a resolver that requires the same nesting structure that resolver gets a :com.wsscode.pathom3.error/attribute-unreachable error? Query:
[{:sf.resources/by-product-id
[{:sf/resource [:resource/meta]}]}
:resource.meta/category-set]
Heading data for the resolver that fails
(pco/defresolver resource-category-set
[_ {resources :sf.resources/by-product-id}]
{::pco/input [{:sf.resources/by-product-id
[{:sf/resource
[:resource/meta]}]}]
::pco/output [:resource.meta/category-set]})
:sf.resources/by-product-id doesn't directly provide :resource/meta , it instead goes through a few resolvers to get subfields. Would that be part of it?
Does querying just `
[{:sf.resources/by-product-id
[{:sf/resource [:resource/meta]}]}]
work?Yes, that works
Found it. I was nesting improperly in my resolver. I think the query itself had enough info to handle my improper nested query and still return something 'sane', but the resolver choked on the incorrect nesting.