[Fusion] Avoid a duplicate selection row read when initializing composite objects

[michaelstaib]

No description provided.

[Copilot]

Pull request overview

This PR optimizes Fusion result-object initialization by avoiding an extra meta-db lookup when a CompositeResultElement already has direct selection metadata available, reducing redundant reads on a hot path in result completion.

Changes:

• Added a fast-path in TryGetSelectionContext to derive type directly from target.Selection when present, bypassing target.Type.

Comments suppressed due to low confidence (1)

src/HotChocolate/Fusion/src/Fusion.Execution/Execution/Results/ValueCompletion.cs:409

• This adds an extra metadb selection-row read when target.Selection is null: the code reads target.Selection (null), then calls target.Type (which reads Selection again), and then the loop reads current.Selection again. Since TryGetSelectionContext already knows target.Selection is null in this branch, you can avoid the redundant reads by deriving the type from the parent and starting the selection walk from target.Parent.

        type = target.Type;

        if (type is null)
        {
            selection = null;

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.