This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-04
Channels
- # announcements (5)
- # aws (12)
- # beginners (76)
- # boot (29)
- # cider (24)
- # circleci (9)
- # clojure (64)
- # clojure-dev (27)
- # clojure-europe (3)
- # clojure-houston (1)
- # clojure-italy (33)
- # clojure-nl (19)
- # clojure-poland (1)
- # clojure-spec (6)
- # clojure-uk (20)
- # clojurescript (103)
- # clojutre (1)
- # code-reviews (60)
- # cursive (76)
- # data-science (20)
- # datomic (20)
- # duct (58)
- # figwheel-main (4)
- # fulcro (36)
- # graphql (6)
- # kaocha (4)
- # onyx (1)
- # pathom (15)
- # quil (3)
- # re-frame (15)
- # reagent (15)
- # reitit (9)
- # remote-jobs (2)
- # rewrite-clj (16)
- # ring-swagger (7)
- # shadow-cljs (132)
- # spacemacs (12)
- # sql (5)
- # vim (9)
- # xtdb (12)
- # yada (4)
Is there a way to do multiple mutations so that a field in one mutation can be used in subsequent mutations? Something like this where the id from create_group
is to be used in add_to_group
:
mutation {
create_group {
id
}
add_to_group(id: "someId", value: 1) {
value
}
}
Or do I have to do two executes for this to happen?I don’t think the graphql spec allows this. You would have to create a mutation like “create and add to group”
mutations do not compose 😞 It's not only GQL limitation. EQL Ecosystem also has this limitation
@souenzzo EQL has (Dotomic style) tempid however 🙂
@myguidingstar yep, it solve one problem But there is no (good/stable) implementations and it's hard to guarantee consistence in both mutations (or the behavior case one fail)