Error when using InputTypes in the response definition about graphql-maven-plugin-project HOT 5 CLOSED

Please not that you should avoid DirectQueries for complex queries. And actually, DirectQueries don't manage field parameters as input types.

In the last commit, I added a specific error message, to precise that.

Consider preparing queries, with parameter as bind variables.

Etienne

from graphql-maven-plugin-project.

Hi Etienne,

Thank you for picking up this item that I reported by e-mail.

I am adding below a dummy query response - for the thread's completeness.

private static final String PJ_QUERY_RESPONSE_DEF = "{" +
" id" +
" time " +
" machine {" +
" id" +
" name" +
" }" +
" jobs { " +
" data " +
"(filter: {" +
" domain: "Mining"" +
" })" +
"{" +
" serviceId" +
" subData {" +
" indicator" +
" id" +
" }" +
" }" +
" }" +
" }";

How should the bind parameters map look like in this situation?
I tried using a prepared query and binding either domain or filter, but the same error message occurs; so maybe I am misusing the API?
Any help would be appreciated.

from graphql-maven-plugin-project.

I reformated your String for better readabilty:
"{id time machine {id name} jobs {data(filter: {domain: "Mining"}){serviceId subData {indicator id}}}}"

The issue here is that the plugin can't currently read the {domain: "Mining"} json part.

So you have to replace the query response by this one:
"{id time machine {id name} jobs {data(filter: ?filterParam){serviceId subData {indicator id}}}}"

This means that there is a Bind Variable of name "filterParam" that must be provided at runtime.
You don't have to provide the map at runtime : the client method allows you to add parameters at the end. The method will create the Map on its own.
These parameters must be couples of values :

• The parameter name (here: "filterParam")
• The parameter value (Here: an object with a "domain" field, whose value is "Mining")

You can see samples in the Forum client project, in the com.graphql_java_generator.samples.forum.client.graphql.PreparedQueries

from graphql-maven-plugin-project.

Hi Etienne,

Thank you for the provided example! It answered my questions!

I consider this Issue Resolved.

Regards,
Amelia

from graphql-maven-plugin-project.

This issue is solved in version 1.2

from graphql-maven-plugin-project.