Consume SerializationOptions for Body Parameters and Responses

[jorgerangel-msft]

This was added as part of tcgc version 0.68.0. Both body parameters and responses now support serialization options. We should update the emitter to consume and propagate this information to MTG. Then in MTG, we should consider replacing any places where we were using the content type header for body params + responses to determine the wire info.

[github-actions]

🎯 Issue Triage

This is a feature request to update the C# client emitter to consume SerializationOptions introduced in tcgc v0.68.0, propagating serialization information for body parameters and responses to MTG, replacing content-type-based wire format detection.

Category: Feature Request
Area: emitter:client:csharp

🔍 Analysis

• tcgc version: 0.68.0 added SerializationOptions for body parameters and responses
• Affected component: @typespec/http-client-csharp emitter + MTG (model/type generation)
• Impact: Improves accuracy of wire format serialization — currently inferred from content-type headers, which is less precise than the explicit SerializationOptions metadata
• Scope: Two parts — (1) emitter consuming and propagating SerializationOptions, (2) MTG using it instead of content-type header heuristics

📝 Suggested next steps

• Update the C# emitter to read SerializationOptions from tcgc for body params and responses
• Pass the serialization info through to MTG
• Replace content-type-based wire format logic in MTG with the explicit SerializationOptions data
• Add/update tests to cover the new serialization option propagation

Generated by Agentic Triage