Development for alias on client side is under progress
@@ -17,7 +17,7 @@ That is: graphql-java-generator generates the boilerplate code, and lets you con
* In __client mode__ : graphql-java-generator generates a class for each query, mutation type and/or subscription type. These classes contain the methods to call the queries, mutations and subscriptions. That is: __to call the GraphQL server, you just call one of this method__. In client mode, the plugin generates:
* The __POJOs__ from the GraphQL schema. That is: one class, interface or enum for each item in the provided GraphQL schema file(s)
* The __utility classes__ that allows you to execute queries, mutations and subscriptions, and to retrieve their result (including the GraphQL response's _extensions field)
- * The support for the full GraphQL specification (relay cursors, subscription, custom scalars, fragment, directive, GraphQL variables...). The only limitation is that aliases are not managed yet on client side. An enhancement will come about this issue.
+ * The support for the full GraphQL specification (relay cursors, subscription, custom scalars, fragment, directive, GraphQL variables...). The only limitation is that aliases are not managed yet on client side: the development is under progress, and should be available soon.
* The capability to use __bind parameters__ within your queries, mutations and subscriptions, in an easier way than the GraphQL variables
* It can be used within a __spring boot app__, or in non-spring apps. When using as a spring boot app, each Spring component can be overridden. This allows fine tuning, like connecting to __OAuth__ server, changing the _HttpClient_, and much more
* In __server mode__ : graphql-java-generator generates an almost ready to start GraphQL server. The developer has only to develop request to the data. That is :
