Graphback: Code generation engine V2.0

[ankitjena]

Background

We are using graphql-code-generator version 0.18.2 in our code base to help generate the schema. Particularly we are using the method schemaToTemplateContext to parse datamodel file and use handlebars to generate schema.

Version 1.0

graphql-code-generator has released version 1.0.0 which removes the above mentioned method as stated in docs

Remove the old, deprecated code from this repostory (everything related to flattenDocuments and buildSchemaContext).

Current version's method generate string in output file format. Check PR #84

Requirement

• We need to use version 1.0.0 to generate Resolver Typings to generate resolvers(these are generated to an output file)
• Figuring out Schema generation in current version.

[wtrocki]

We decided we need to rearchitecture currently graphback package to rely on the plugins and utilize latest version of the tool.

Target package structure:

This will give us greater flexibility and we can reuse/contribute back some specific parts of the code.

[ankitjena]

Upon further inspection we might not need separate packages after all. Using the visitor pattern we can replace the deprecated context generation part. And redesign the core along the way. Graphql-code-generator doesn't provide much value at out current scope. But we might use it to provide out of the box solutions in future.

[ankitjena]

Closing this

[dotansimha]

@ankitjena the changes in https://github.com/aerogear/graphback/pull/112 looks great :)
What do you think about wrapping these visitors as graphql-codegen plugin? this way it will be available as ready-to-use and independent generator.
It might also make it easier for you to load the schema (because the codegen does that with graphql-toolkit, and it can easily load schema from any file - code/graphql ast/exports/url).

[wtrocki]

+100 for wrapping our code and using extended features of codegen, however we might have some advanced flows we would like to support first and then see if we can contribute them back to codegen along with the top level generation plugin