This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-21
Channels
- # announcements (10)
- # aws (38)
- # beginners (220)
- # calva (2)
- # cider (26)
- # clj-kondo (194)
- # cljs-dev (4)
- # clojure (190)
- # clojure-dev (7)
- # clojure-europe (3)
- # clojure-italy (6)
- # clojure-nl (4)
- # clojure-uk (8)
- # clojured (1)
- # clojurescript (29)
- # code-reviews (31)
- # community-development (9)
- # core-async (24)
- # cursive (38)
- # data-science (51)
- # datomic (52)
- # dirac (2)
- # emacs (3)
- # events (1)
- # figwheel-main (4)
- # fulcro (49)
- # graphql (13)
- # heroku (1)
- # hoplon (19)
- # immutant (3)
- # leiningen (1)
- # nrepl (59)
- # off-topic (12)
- # onyx (2)
- # pathom (51)
- # reitit (15)
- # shadow-cljs (88)
- # spacemacs (6)
- # sql (3)
- # tools-deps (107)
- # xtdb (11)
I nurture a deep and abiding hatred of Java logging frameworks generally, but have expended a lot of effort getting our current configuration working (using clojure.tools.logging on top of slf4j/logback) and am not anxious to configure another thing. As long as pedestal uses slf4j under the covers I'm fine with it, though.
Is it a function of the GraphQL spec that Argument %s is must be a scalar type, an enum, or an input object.
?
how does your query look
it sounds like you are trying to define a field that has an argument that is not a Scalar, Enum or an Input Object
List is allowed
Ah, my mistake was that I was trying to use a regular :object
instead of :input-object
, thanks.
yeah, I figured something like that
you can’t because regular objects can have circular references
I was wondering: what are people here doing with user-generated errors caused by mutations. Ideally you match them to the input given in the mutation, but the ‘standard’ errors only have a path to the field.
I took a bit of a look around, the GitHub schema just gives you a normal error with just a path to the mutation. It doesn’t point you any closer to what input field was not valid
Some people suggest modelling errors in your schema, e.g. https://github.com/graphql/graphql-spec/issues/298#issuecomment-296715901