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

_service query should return non-nullable _Service type #227

Closed
dariuszkuc opened this issue Jul 26, 2022 · 0 comments · Fixed by #231
Closed

_service query should return non-nullable _Service type #227

dariuszkuc opened this issue Jul 26, 2022 · 0 comments · Fixed by #231
Assignees
Labels
type: bug Something isn't working

Comments

@dariuszkuc
Copy link
Member

Per the subgraph specification:

A new field must be added to the query root called _service. This field must return a non-nullable _Service type. The _service >field on the query root must return SDL which includes all of the service's types (after any non-federation transforms), as well as >federation directive annotations on the fields and types. The federation schema modifications (i.e. new types and directive >definitions) should not be included in this SDL.

Schema transformer currently creates the field returning nullable type

_service: _Service
@dariuszkuc dariuszkuc added the type: bug Something isn't working label Jul 26, 2022
@dariuszkuc dariuszkuc self-assigned this Jul 26, 2022
dariuszkuc added a commit to dariuszkuc/federation-jvm that referenced this issue Jul 27, 2022
`FederationSdlPrinter` is a copy of a `graphql.schema.idl.SchemaPrinter` from `graphql-java` v17 with some custom filtering logic that was required for Federation v1.

`graphql-java` v18 introduced concept of applied directive to make a distinction from the directive definition (previously same `GraphQLDirective` type was used for both). This PR drops our custom copy of the schema printer and instead updates our logic to rely on the built-in schema printer provided by the `graphql-java`. Using custom predicates for filtering directives and schema elements we can replicate our custom functionality without the need of a custom printer.

Related:

* resolves: apollographql#227
* resolves: apollographql#216
* supersedes: apollographql#223
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant