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

Require Interface to implement at least 1 Object #424

Merged
merged 2 commits into from
Apr 4, 2018

Conversation

mattkrick
Copy link
Contributor

Matches graphql-js PR: graphql/graphql-js#1280
For background, see graphql/graphql-js#1277

@leebyron
Copy link
Collaborator

leebyron commented Apr 4, 2018

Thanks for accounting for this schema validation addition!

@mjmahone
Copy link
Contributor

mjmahone commented Jun 8, 2018

I think we should change the spec and revert this changes: there is no reason a schema should be required to have objects implementing each interface. A very common pattern is to create an interface first, start programming against that, then weeks later actually implement that interface. This is also a really nasty breaking change for large, existing schemas.

mjmahone added a commit to graphql/graphql-js that referenced this pull request Jun 8, 2018
It is unclear whether the spec validation from graphql/graphql-spec#424 as implemented by #1277 is what we want to have for the GraphQL Schema long term. This RFC lets us explore that option more, to see whether the breaking schema change is the right path forward.
mjmahone added a commit that referenced this pull request Jun 8, 2018
Re-applies #424, but as an RFC. This change is a major spec breaking change, and if it is desireable, we should provide an upgrade path for existing schemas.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants