[michaelstaib]

When a field uses [Parent(requires: ...)] on a list with [UsePaging] or [UseOffsetPaging] and [UseProjection], the required property was not loaded, so the resolver saw a default value. Paging builds the database query from a hidden internal field, and since #9978 every field below it is internal too. The requirements optimizer skipped all internal fields, so it never saw the fields the client selected. It now only skips the hidden requirement fields it adds itself.

public int GetNameLength([Parent(requires: nameof(Item.Name))] Item item)
    => item.Name.Length;

[UsePaging]
[UseProjection]
public IQueryable<Item> GetItems() => ...;

{
  items {
    nodes {
      nameLength
    }
  }
}

For an item named abc, nameLength was 0 before this fix and is 3 now.

[github-actions]

Patch coverage

100.0% of changed lines covered (1/1)

File	Covered	Changed	Patch %
…/Optimizers/QueryableRequirementsProjectionOptimizer.cs	1	1	100.0% 🟢

---

Project coverage: 59.4% (317091/533687 lines)