-
Notifications
You must be signed in to change notification settings - Fork 55
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
update @requires test to verify the functionality #150
Conversation
Whats the approach to adding these changes to implementations? will that be done in this PR? How can library maintainers help? |
@kdawgwilk 👋 I'll split the PR into the schema + test update and will have separate implementations PR. Once the test PR is merged, you will be able to update the implementations without waiting for additional changes from my side. Thanks for the help! |
261172d
to
6adf888
Compare
Does |
@ddebrunner yes, I'll update it once the #152 is merged |
6adf888
to
6300201
Compare
Updating `users` and `products` subgraph schemas to allow for testing the support of `@requires` functionality in the implementing subgraph. This is a breaking change as we modify the schema so all the existing implementations will be impacted. Changes: * `users` subgraph ```graphql type User @key(fields:"email") { email:ID! name: String totalProductsCreated: Int yearsOfEmployment: Int! # <-- new field } ``` * `products` subgraph ```graphql extend type User @key(fields: "email") { averageProductsCreatedPerYear: Int @requires(fields: "yearsOfEmployment") # <-- test `@requires` functionality email: ID! @external name: String @OverRide(from: "users") totalProductsCreated: Int @external yearsOfEmployment: Int! @external # <-- field from the users subgraph used by @requires } ``` Related Issues: * apollographql#128
6300201
to
7654316
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for adding this @dariuszkuc!
Updating
users
andproducts
subgraph schemas to allow for testing the support of@requires
functionality in the implementing subgraph. This is a breaking change as we modify the schema so all the existing implementations will be impacted.Changes:
users
subgraphproducts
subgraphImplementation updates will follow in separate PRs.
Related Issues: