You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the plugin automatically copies the schema file to a folder called graphql-apigen-schema in the target output path (classes) folder. Also, if the schema file references any other files, they are not included.
Ideally, the output path for the schema should be configurable, and it should include all referenced *.graphql files.
The text was updated successfully, but these errors were encountered:
Making the output path configurable, should be a simple change to ApiGenMojo.java, pull requests are welcomed :).
Regarding schema files that reference other files, I assume you mean referencing schema files from other maven modules? If so, the expectation is for the generated code to come from the maven module dependencies and therefore the dependent code is not regenerated.
Currently the plugin automatically copies the schema file to a folder called
graphql-apigen-schema
in the target output path (classes
) folder. Also, if the schema file references any other files, they are not included.Ideally, the output path for the schema should be configurable, and it should include all referenced *.graphql files.
The text was updated successfully, but these errors were encountered: