You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See this comment. The parameters ipv4 & ipv6 are generated as iPv4 and iPv6 instead of IPv4 and IPv6. It's possible the ToIdentifierName is not respecting this transformation.
Parameters named ipv4 and ipv6 are incorrectly generated as iPv4/iPv6 instead of the expected IPv4/IPv6 in the C# client emitter, suggesting ToIdentifierName doesn't handle acronym casing correctly.
Category: Bug Area: emitter:client:csharp
⚠️ No reproduction provided. A minimal repro would help diagnose this issue.
🔍 Analysis
The bug is in identifier name generation within the C# client emitter (@typespec/http-client-csharp).
ToIdentifierName likely splits on word boundaries but doesn't recognize known acronyms like IPv4/IPv6, causing incorrect PascalCase output (iPv4 instead of IPv4).
A fix would require maintaining an acronym/abbreviation list or special-casing known patterns so they are preserved or correctly capitalized.
Activity
github-actions commentedon Aug 14, 2026
🎯 Issue Triage
Parameters named
ipv4andipv6are incorrectly generated asiPv4/iPv6instead of the expectedIPv4/IPv6in the C# client emitter, suggestingToIdentifierNamedoesn't handle acronym casing correctly.Category: Bug
Area:
emitter:client:csharp🔍 Analysis
@typespec/http-client-csharp).ToIdentifierNamelikely splits on word boundaries but doesn't recognize known acronyms likeIPv4/IPv6, causing incorrect PascalCase output (iPv4instead ofIPv4).📝 Suggested next steps
ToIdentifierNameis defined in the C# emitter codebase.IPv4,IPv6,HTTP,URL).Fix IPv4 and IPv6 casing in generated C# parameters (microsoft#11673)