Allow a directory of schemas to be passed in

[joffrey-bion]

Is your feature request related to a problem? Please describe.
When we want to break the schema down into many parts (for scalability), it's very inconvenient to have to maintain a list of schemas to process (either in the code or in a gradle/maven plugin).

Describe the solution you'd like
It would be nice to be able to specify a directory so that graphql-java-codegen processes all the schema files inside.

A couple of useful related options to consider:

• recursive: whether directories should be explored recursively to find schemas
• schemaFilePattern: a pattern (Java style) to match the schema files to process (would most likely default to .*\.graphqls)
• excludeFiles: a list of schema files to exclude

Describe alternatives you've considered
The alternatives so far are:

• to list all files manually (most likely in the maven plugin)
• to write custom code (maybe as another plugin/task) to build the list of files

[kobylynskyi]

This would be a very useful feature to have!
I hope that I will have time for this one late this week or early-next week (as you know right now I am working on 25 which is quite big 😄)

[joffrey-bion]

Maybe I can contribute this one, although it may require a bit of discussion about how to approach this in terms of implementation.

Currently the schemas are provided as constructor params, not as input to the generate method.
I see a couple options to change that:

• provide another constructor with Supplier<List<String>> schemaSupplier instead of schema list, and we could have any implementation of that supplier to support any option we want
• remove schemas from constructor arguments, and pass them as parameters to the generate() method. We could also use the Supplier approach for one of the overloads of generate()

[kobylynskyi]

@joffrey-bion sure, I would appreciate it if you can work on this feature.
From the implementation POV, I like your option to remove schemas from the constructor and pass them as a parameter to generate() method. We are free to change that because as of now there are only 2 usages of this class (gradle and maven plugins)

[kobylynskyi]

@joffrey-bion
I would like to reopen this feature request in order to track the changes which need to be made in gradle and maven plugins (after #34 will be merged)

[joffrey-bion]

Thanks for reopening, let's keep track of the gradle plugin updates here.