Skip to content
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

Feature Request: Support multiple schema files #88

Closed
StevenACoffman opened this issue Sep 10, 2021 · 0 comments · Fixed by #134
Closed

Feature Request: Support multiple schema files #88

StevenACoffman opened this issue Sep 10, 2021 · 0 comments · Fixed by #134
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Issues that anyone could pick up and implement if useful to them

Comments

@StevenACoffman
Copy link
Member

While consistency with gqlgen is really a goal as such, but it would be convenient if we similarly supported multiple schema files they way it does:

package: genqlient
schema:
- ../../pkg/graphql/shared-schemas/side_by_side_directives.graphql
- ../../pkg/graphql/shared-schemas/user_deletion.graphql
- ../../pkg/graphql/shared-schemas/automap.graphql
- schema.graphql
- homepage_render.graphql
# The files from which we pull operations (relative to genqlient.yaml).
operations:
- genqlient.graphql

A client that is generated from the federated composed_schema.graphql has a lot more churn than what is required to communicate with a single service.
It might be nice to generate a "just this service" client, but that would require supporting multiple schema files.

@benjaminjkraft benjaminjkraft added enhancement New feature or request good first issue Good for newcomers help wanted Issues that anyone could pick up and implement if useful to them labels Sep 11, 2021
csilvers pushed a commit that referenced this issue Oct 4, 2021
* ⚡️ Fixes #88. Accept array of string as valid input schema path.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Issues that anyone could pick up and implement if useful to them
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants