You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a subgraph "A" that has a query widgetById(widgetId: ID!): Widget! and another subgraph "B" that has a type with a widgetId field type Thing { widgetId: ID! }. I want to extend this type with a field widgetName that is resolved from the Widget.name field.
I added this to schema.extensions.graphql in subgraph "A"
extend type Thing
{
widgetName(widgetId: ID! @require(field: "widgetId")): String @resolve(select: "widgetById(widgetId: $widgetId) { name }")
}
and when I try to query that field, I get an error:
{
"message": "The field `widgetName` does not exist on the type `Query`.",
"locations": [
{
"line": 1,
"column": 46
}
],
"extensions": {
"type": "Query",
"field": "widgetName",
"responseName": "widgetName",
"specifiedBy": "http://spec.graphql.org/October2021/#sec-Field-Selections-on-Objects-Interfaces-and-Unions-Types"
}
}
I would expect the fusion graph to produce the query that I'm passing into the @resolve directive.
Steps to reproduce
Relevant log output
No response
Additional Context?
No response
Version
13.6.0-preview.23
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Product
Hot Chocolate
Describe the bug
I have a subgraph "A" that has a query
widgetById(widgetId: ID!): Widget!
and another subgraph "B" that has a type with a widgetId fieldtype Thing { widgetId: ID! }
. I want to extend this type with a fieldwidgetName
that is resolved from theWidget.name
field.I added this to schema.extensions.graphql in subgraph "A"
which produces this in the fusion graph:
and when I try to query that field, I get an error:
I would expect the fusion graph to produce the query that I'm passing into the
@resolve
directive.Steps to reproduce
Relevant log output
No response
Additional Context?
No response
Version
13.6.0-preview.23
The text was updated successfully, but these errors were encountered: