This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-16
Channels
- # announcements (7)
- # babashka (8)
- # beginners (48)
- # calva (4)
- # cider (6)
- # circleci (2)
- # clj-commons (14)
- # clj-kondo (3)
- # clj-on-windows (7)
- # cljs-dev (34)
- # clojure (49)
- # clojure-dev (25)
- # clojure-europe (48)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-norway (33)
- # clojure-uk (2)
- # clojurescript (37)
- # community-development (5)
- # conjure (17)
- # cursive (2)
- # data-science (1)
- # editors (10)
- # emacs (50)
- # events (22)
- # honeysql (11)
- # introduce-yourself (1)
- # jobs-discuss (13)
- # lsp (42)
- # malli (9)
- # off-topic (7)
- # pathom (11)
- # portal (5)
- # re-frame (3)
- # reagent (22)
- # reitit (8)
- # reveal (1)
- # rewrite-clj (4)
- # shadow-cljs (38)
- # xtdb (21)
The client always requests certain attributes (like :tempids
) but often none of the resolvers executed return the attribute, which leads to `
::p.error/attribute-unreachable
a lot of the time. Is there a way around this? I wanted to introduce a resolver that returns :tempids {}
without any input. But what will happen when the mutation DOES return :tempids {….}
? which will be returned to the client?Priority should help here. I played around with a similar idea of a resolver that would generate and return ids if one wasn’t provided but it was a bit too confusing to debug. I recall caching having an interesting role. If I wanted multiple new ids, my resolver would return the initial cached value. I ended up scrapping the idea before messing with the caching.
Is it possible the client could optionally request tempids?
(pco/? :tempids)
Does (pco/? :tempids)
work over the wire?
using transit here
the issue is that there are many transformations happening between my client code and server that transform query->ast->query again
oh so it’s a param
that should work I think
I recall it working in an eql query
Something like (pco/? :tempids)
operates at the Pathom planner level so it is internal to how Pathom decides when there is sufficient input for a resolver