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

Upgrade to graphql-java 16.1 #66

Merged
merged 3 commits into from
Jan 12, 2023
Merged

Conversation

jamesdh
Copy link
Contributor

@jamesdh jamesdh commented Jan 28, 2021

The biggest breaking changes from 14.0 that are relevant to this project include:

  • The assertion that a schema must have a queryType. This essentially breaks our ability to do operations.query.enabled false when there are no other query operations present. This felt a little strange to me and I asked on their spectrum why this is required, as it seems perfectly legit to have a write-only API.
    Update: I guess it's part of the spec after all

  • The assertion that all object types must have fields defined. This is especially relevant for some input types since they would not have at a minimum an id property like object output types do. Per the GraphQL spec, the very first rule for adhering to object type validation is:

    An Object type must define one or more fields.

    ...so this one makes a bit more sense.

And a minimum of a queryType is required for the schema to be generated
@puneetbehl puneetbehl changed the base branch from master to 3.0.x January 12, 2023 10:45
@puneetbehl puneetbehl merged commit 69cd202 into grails:3.0.x Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants