-
Notifications
You must be signed in to change notification settings - Fork 254
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
Try implementing subgraph-js using the federation internals #1697
Conversation
👷 Deploy request for apollo-federation-docs pending review.Visit the deploys page to approve it
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
e62004f
to
fffa695
Compare
@@ -60,6 +61,58 @@ function addTypeNameToPossibleReturn<T>( | |||
return maybeObject as null | (T & { __typename: string }); | |||
} | |||
|
|||
export function entitiesResolver({ |
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.
Is there any functional change in this file that I'm not seeing or is it just a non-functional refactor?
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.
There is not change to the resolver code, but it extract it as a method because it's called in buildSubgraphSchema
directly now.
@@ -593,7 +593,7 @@ describe('@core/@link handling', () => { | |||
|
|||
type Query { | |||
_entities(representations: [_Any!]!): [_Entity]! | |||
_service: _Service | |||
_service: _Service! |
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.
Why does this change?
No description provided.