Skip to content

Latest commit

 

History

History
35 lines (32 loc) · 2.74 KB

TODO.md

File metadata and controls

35 lines (32 loc) · 2.74 KB
Raw

Here are the next tasks listed, as a TODO list:

TODO list for the 2.x branch

  • (re)Publish the wiki for the 2.6 release
  • Check that the two generated graphQLClient (httpGraphQLClient and webSocketGraphQLClient) are properly documented in the tutorials
  • Add a test for the GraphQL json schema
  • Indicates in the Gradle tutorials that there are two versions of the plugin
  • Check the links in the wiki (eg: https://graphql-maven-plugin-project.graphql-java-generator.com/client.html)
    • And close issue in the GraphQL-Forum-Gradle-Tutorial-client project)
  • Ajouter le paramètre generateDataFetchersForFields dans les tutoriels
  • Dozer is deprecated. Replace it by mapstruct or modelmapper
  • Replace DataFetchersDelegateRegistry attributes by proper autowired spring fields
  • The arguments for a subobject are available in the DataFetchingEnvironment, thanks to the getArgument(argName) method. For a scalar field, the idea is to add a getter for the field, with the DataFetchingEnvironment as a parameter. This getter would be in the generated POJO. It would be nice to add the developper to configure the content of this getter.
  • Optimize getStringContentForGraphqlQuery: use a StringBuilder instead of returning and concatenating strings
  • Use [[TOC]] for the wiki pages (and the README)
  • Refresh the GitHub and Shopify samples
  • Review the plugin documentation (goal and parameters)
  • Issue Gradle-project #15: redundant cast to Long
  • Issue #113: accept a schema.json as an input for code generation (instead of graphqls files)
  • Issue #125: object_content.vm.java is hardcoded in templated
  • Idea #183: replace hard coded fields by maps. This would save memory for objects with lots of field (4000 fields in the identified use case)
  • [Gradle] issue #14 : build is not compatible with the --configuration-cache gradle parameter (experimental feature)
  • DirectiveRegistryInitializer:
    • initialize it only once (not at each creation of a GraphQLRequest)
  • Tutorial: add the documentation about the application.yml file
    • Especially: spring.main.web-application-type = none
  • Execute FieldTest.test_Issue1114_checkGenerateCode() (in plugin-logic, com.graphql_java_generator.plugin.language)
  • add a HowTo compile page on the wiki (to build the plugin project, Java 9 or latter is needed, even if the built plugin is compatible with Java 8)
  • @EnableGraphQLRepositories: replace the string (that contains the package name) by a class (so that when changing a package name, the code is still valid)
  • Add a description for the GraphQL mojo
  • Document generateJPAAnnotation

TODO list for the 1.x branch