[http-client-csharp] Paging fails when page items property is inherited

[live1206]

Description

The C# generator reports no-matching-items-property for a paging response when the page-items property is inherited from a base model.

This blocks generation of Azure SDK operations whose response model extends an intermediate Page<T> model, including Azure SDK for .NET issue Azure/azure-sdk-for-net#59567.

Minimal model shape

DerivedPage
  baseModel: BasePage

BasePage
  value: Item[]

pagingMetadata.itemPropertySegments: ["value"]

Root cause

ScmMethodProviderCollection.GetResponseBodyType resolves each paging segment using only modelType.Properties. It does not inspect modelType.BaseModel, so it cannot find an inherited items property even though the input code model and paging metadata are correct.

Expected behavior

Paging item-property resolution should search the current response model and its base-model chain, preserving derived-model precedence.

Validation

A focused ClientModel regression test reproduces the failure by defining value on a base page model and using a derived response model. The expected convenience return type is CollectionResult<Item>.

- by copilot

[github-actions]

🎯 Issue Triage

The C# client emitter reports a no-matching-items-property diagnostic when the paging items property (e.g. value) is defined on a base model rather than the direct response model, blocking Azure SDK generation for affected operations.

Category: Bug
Area: emitter:client:csharp

⚠️ No TypeSpec reproduction provided (this is a C# emitter code generation bug, not a TypeSpec compilation issue).

🔍 Analysis

• Affected component: ScmMethodProviderCollection.GetResponseBodyType in the C# emitter
• Root cause: The paging segment resolution only checks modelType.Properties and does not walk modelType.BaseModel, so inherited properties are invisible to the resolver
• Impact: Any Azure SDK operation whose paging response model uses inheritance (e.g. DerivedPage extends BasePage where value is on BasePage) will fail generation — directly blocking MPG: no-matching-items-property for SavingsPlanModelListResult extends SavingsPlanModelList is Azure.Core.Page<T> Azure/azure-sdk-for-net#59567
• Fix direction: Walk the full base-model chain when resolving paging itemPropertySegments, with derived-model properties taking precedence

📝 Suggested next steps

• Update GetResponseBodyType to traverse modelType.BaseModel recursively when a segment property is not found on the current model
• Add a ClientModel regression test: DerivedPage (no value) → BasePage (has value: Item[]), expect CollectionResult<Item> convenience return type
• Verify fix resolves MPG: no-matching-items-property for SavingsPlanModelListResult extends SavingsPlanModelList is Azure.Core.Page<T> Azure/azure-sdk-for-net#59567

Generated by Agentic Triage