[michaelstaib]

When a field with @require is on a type that has no lookup in its source schema, the planner fetches it through the lookup of the nearest parent that has one. The plan then says that the requirement data sits below that parent, at the object that holds the field. The gateway ignored this and looked for the data on the parent itself. It found nothing, so it never sent the request, and the field came back as null without an error.

The gateway now follows the requirement's path from the parent down to the object and reads the data there. If that object is null, a type condition does not match, or a list is in the way, the gateway skips that item instead of sending a request with missing data. The plans themselves do not change.

Example

Schema a:

type Query {
  products: [Product!]!
}

type Product {
  id: Int! @shareable
  details: Details @shareable
}

type Details {
  weight: Int!
}

Schema b, where Details has no lookup:

type Query {
  productById(id: Int!): Product @lookup @internal
}

type Product @key(fields: "id") {
  id: Int! @shareable
  details: Details @shareable
}

type Details {
  shippingEstimate(weight: Int! @require(field: "weight")): Int!
}

{
  products {
    id
    details {
      shippingEstimate
    }
  }
}

Before, b was never called and every shippingEstimate came back as null, although the field is non-null. Now b receives each product's weight and returns the estimates.

[github-actions]

Patch coverage

100.0% of changed lines covered (79/79)

File	Covered	Changed	Patch %
…/src/Fusion.Execution/Execution/Results/FetchResultStore.cs	79	79	100.0% 🟢

---

Project coverage: 59.4% (317161/533756 lines)