I notice that during maven build and code generation of hello.graphqls The generated file of schema.graphqls is deleted and ultimately only one graphl schema as an API is exposed.
Alternative approach such as adding a new execution block and different output directory as described below also result in exposing of the API from first execution block i.e. schema.graphqls alternatively though files are generated for hello.graphqls also and are present in target folder the API is inaccessible.
@logicatmidod
If you have multiple Query types across graphql schemas, then make sure that you use the extend keyword.
I just verified with extend type Query and it works as expected:
If I create two schema in my project and add the schema paths in plugin configuration while trying to use GraphQL Server
I notice that during maven build and code generation of hello.graphqls The generated file of schema.graphqls is deleted and ultimately only one graphl schema as an API is exposed.
Alternative approach such as adding a new execution block and different output directory as described below also result in exposing of the API from first execution block i.e. schema.graphqls alternatively though files are generated for hello.graphqls also and are present in target folder the API is inaccessible.