-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generating code from external schemas in JARs - META-INF requirement #668
Comments
Usually schema files are added under src/main/resources for graphql projects and hence we scan for the META-INF folder in codegen. Thanks for pointing out the documentation gap, we need to fix that. |
Fixed the docs here: Netflix/dgs@a518e6d |
Ok, I see. At the time of adding this feature, our primary use case was to pick up schemas under META-INF and from other modules in a given project that has schemas under META-INF, so the current implementation addresses that requirement. But for other external dependencies it would not work as you just pointed out. We could enhance this implementation to scan for .graphqls files more generally as well I suppose. |
@srinivasankavitha thanks for taking a second look and reconsidering! |
Hi team,
Curious why there is a requirement for schema files in external jars to exist under the META-INF folder.
This was uncovered in a maven graphql-codegen plugin project here. I'll update our documentation, but wondering why this is a requirement and does it make sense to update the documentation?
The text was updated successfully, but these errors were encountered: