This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-13
Channels
- # announcements (2)
- # aws (4)
- # babashka (14)
- # beginners (186)
- # cljdoc (2)
- # cljsrn (7)
- # clojure (56)
- # clojure-austin (1)
- # clojure-australia (2)
- # clojure-europe (46)
- # clojure-france (5)
- # clojure-nl (16)
- # clojure-norway (7)
- # clojure-spec (76)
- # clojure-sweden (15)
- # clojure-uk (13)
- # clojurescript (60)
- # code-reviews (2)
- # conjure (8)
- # datascript (1)
- # datomic (4)
- # depstar (10)
- # emacs (9)
- # events (4)
- # exercism (1)
- # fulcro (36)
- # graalvm (8)
- # introduce-yourself (3)
- # jobs-discuss (2)
- # kaocha (14)
- # lsp (1)
- # minecraft (8)
- # new-channels (1)
- # off-topic (3)
- # pathom (6)
- # polylith (9)
- # re-frame (48)
- # shadow-cljs (5)
- # specter (26)
- # tools-deps (19)
- # vim (2)
- # vscode (1)
is there a way of having nested batching resolvers? https://github.com/wilkerlucio/pathom/issues/121 suggests thats not the case 😕 I wonder if anything changed with pathom3, or if there is a tool like https://github.com/graphql/dataloader/issues/79#issuecomment-361758674/https://www.juxt.pro/blog/superlifter
hello, this is a non-issue in Pathom 3, the batch mechanism there uses a different idea and can handle cases like nested and even entities that are disperse across the request
4
On a related note, is there any sort of upgrade doc/guide for pathom2 👉 pathom3?
not yet, but I would love to hear feedback and assist anyone wanting to do it
resolvers / mutations are mostly portable, but there may be some work to port plugins
2