This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-14
Channels
- # announcements (1)
- # asami (3)
- # aws (1)
- # babashka (22)
- # beginners (39)
- # calva (21)
- # clj-kondo (10)
- # cljdoc (22)
- # cljs-dev (17)
- # clojure (93)
- # clojure-australia (3)
- # clojure-europe (39)
- # clojure-italy (3)
- # clojure-losangeles (17)
- # clojure-nl (14)
- # clojure-russia (2)
- # clojure-uk (5)
- # clojurescript (35)
- # community-development (7)
- # conjure (2)
- # cursive (13)
- # data-science (1)
- # datomic (25)
- # emacs (5)
- # events (4)
- # figwheel-main (2)
- # fulcro (12)
- # graphql (7)
- # gratitude (2)
- # inf-clojure (6)
- # leiningen (6)
- # lsp (49)
- # malli (13)
- # membrane (30)
- # minecraft (1)
- # pathom (3)
- # pedestal (26)
- # polylith (13)
- # portal (2)
- # quil (3)
- # random (1)
- # re-frame (13)
- # reagent (43)
- # reitit (6)
- # releases (1)
- # reveal (2)
- # ring (3)
- # shadow-cljs (30)
- # specter (5)
- # sql (8)
- # tools-build (1)
- # tools-deps (13)
- # videos (1)
Using pathom3, is there a way to have a mutation join differently? Use case: having an update-user mutation, that we can send multiple updates through with separately, and see the result of each So:
[('update-user {:id 1 :active true})
('update-user {:id 2 :active false})]
then get a response for each
{'(update-user 1) :ok '(update-user 2) :error}
Currently it returns a single entry from whatever came last
{'update-user :error}
@lsenjov in pathom2 you can, if you can't in pathom3, it may be a issue
in pathom2 it will aways have this naming issues. as both mutations have the same name, the second will overwrite the result of the first.
But talking in a graph-api perspective, I would say that it is a anti-pattern.
I would do something like [(update-many-u\ers {:users [{:id 1...} ...]})]
, then you can return something like {update-many-users {:deleted [{:id 1... } ..]}}
☝️ 1