graphql

timgilbert 2019-10-21T16:39:44.040800Z

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.

➕ 3
hlship 2019-10-21T16:51:56.041100Z

Also this: https://github.com/AvisoNovate/logging

xiongtx 2019-10-21T18:07:28.041700Z

Is it a function of the GraphQL spec that Argument %s is must be a scalar type, an enum, or an input object.?

xiongtx 2019-10-21T18:07:52.042100Z

I.e. passing a list is not allowed?

2019-10-21T18:28:52.042300Z

how does your query look

2019-10-21T18:39:35.042500Z

it sounds like you are trying to define a field that has an argument that is not a Scalar, Enum or an Input Object

2019-10-21T18:41:23.042700Z

List is allowed

2019-10-21T18:52:51.044400Z

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.

2019-10-21T18:53:18.044500Z

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

2019-10-21T18:54:28.044700Z

Some people suggest modelling errors in your schema, e.g. https://github.com/graphql/graphql-spec/issues/298#issuecomment-296715901

xiongtx 2019-10-21T20:31:00.045300Z

Ah, my mistake was that I was trying to use a regular :object instead of :input-object, thanks.

2019-10-21T20:41:29.045500Z

yeah, I figured something like that

2019-10-21T20:41:50.045700Z

you can’t because regular objects can have circular references