Consider Having Exact Override Back Compat Naming

[jorgerangel-msft]

Currently, back compat is applied regardless of any naming done via client.tsp. We should consider having any name applied via exact take precedence over any naming applied by back compat, since exact is an advanced scenario where the consumer is possibly already deciding to override some default naming rules.

[github-actions]

🎯 Issue Triage

This is a feature request to change naming precedence in the C# client emitter so that exact naming (set via client.tsp) takes priority over back-compat naming rules.

Category: Feature Request
Area: emitter:client:csharp

🔍 Analysis

• Affected component: @typespec/http-client-csharp — back-compat naming logic
• Request: When a user explicitly sets a name using exact in client.tsp, that should win over any back-compat name transformation, since exact signals a deliberate override of default naming rules.
• Impact: Users customizing client naming via client.tsp may currently get unexpected names because back-compat renaming is applied after their explicit override.
• No duplicate found for this specific request.

📝 Suggested next steps

• Identify where back-compat naming is applied in the C# emitter pipeline relative to exact name resolution
• Determine the correct precedence order and implement the fix
• Add tests verifying exact names are preserved over back-compat transforms

Generated by Agentic Triage