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.
Also this: https://github.com/AvisoNovate/logging
Is it a function of the GraphQL spec that Argument %s is must be a scalar type, an enum, or an input object.
?
I.e. passing a list is not allowed?
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
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
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