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
Resolvers of merged types not running in nested query #1697
Comments
Interestingly, with this query, just adding the query {
me {
reviews {
product {
upc
name
shippingEstimate
}
}
}
} it does seem to attempt to delegate to the Reviews service, but I get this error:
|
huh! will investigate. thanks! |
yaacovCR
added
the
waiting-for-release
Fixed/resolved, and waiting for the next stable release
label
Jun 28, 2020
yaacovCR
added a commit
that referenced
this issue
Jun 28, 2020
Fixed (hopefully) by #1699, available as alpha. Quickly update your package.json by running:
|
Seems to work, thank you! |
Thank you for reporting! |
yaacovCR
removed
the
waiting-for-release
Fixed/resolved, and waiting for the next stable release
label
Jul 3, 2020
Release in 6.0.12, thanks again for reporting! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As an exercise, I took this federation-demo repo and tried converting it to use schema stitching provided by this library. See my branch here.
This query is working:
While this is not:
And, it seems that it's not even attempting to delegate to the Reviews service to resolve the
shippingEstimate
field.I thought that maybe I needed to do something special for nested queries, but other nested queries seem to be working just fine:
The above works just fine.
Is there something I'm missing here, or is this a bug?
The text was updated successfully, but these errors were encountered: