These are chat archives for graphql-java/graphql-java

7th
Nov 2016
Yurii Rashkovskii
@yrashk
Nov 07 2016 15:31
guys, was wondering if we can extend ValuesResolver to be able to handle input object variables as instances of whatever they are?
I wrote a variable resolution utility that allows me to map variables back to classes (since I am using graphql-java-annotations I have “backing classes”)
basically, if it isn’t Map, pass it through as is
the rationale is this: I have a class for mutation, say TestCommand which has a field of type Val (simple POJO with some other fields in it)
I want to pass an object corresponding to TestCommand (something like {clientMutationId: “1”, “value”: {“v”: “Value”}}) as a variable
Yurii Rashkovskii
@yrashk
Nov 07 2016 15:36
and do something like mutation M($input: testInput!) { test(input: $input) { clientMutationId result } }
Yurii Rashkovskii
@yrashk
Nov 07 2016 15:41
cc @dminkovsky @andimarek ^^