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
{{ message }}
Repository navigation
Ensure Generated Enums Members in Extensible Enums Follow Naming Guidelines #12602
The C# client emitter can preserve all-uppercase names for extensible-enum members, producing public API names that do not follow .NET PascalCase guidelines. Exact-name requests should remain unchanged.
Category: Bug
Area: emitter:client:csharp
⚠️ No reproduction provided. A minimal repro would help diagnose this issue.
🔍 Analysis
This affects extensible-enum member-name generation in @typespec/http-client-csharp; wire values should remain unchanged. The likely gap is in the generated-name casing path used by extensible enums, which appears to retain all-uppercase identifiers when exact is not set. #12070 is related because it changed acronym normalization for enum and union members, but it addresses acronym boundaries rather than this general PascalCase behavior and is not a clear duplicate.
📝 Suggested next steps
Add a minimal TypeSpec case that generates an all-uppercase extensible-enum member.
Add focused tests for PascalCase conversion, unchanged wire values, and exact preservation.
Activity
github-actions commentedon Nov 17, 2026
🎯 Issue Triage
The C# client emitter can preserve all-uppercase names for extensible-enum members, producing public API names that do not follow .NET PascalCase guidelines. Exact-name requests should remain unchanged.
Category: Bug
Area:
emitter:client:csharp🔍 Analysis
This affects extensible-enum member-name generation in
@typespec/http-client-csharp; wire values should remain unchanged. The likely gap is in the generated-name casing path used by extensible enums, which appears to retain all-uppercase identifiers whenexactis not set. #12070 is related because it changed acronym normalization for enum and union members, but it addresses acronym boundaries rather than this general PascalCase behavior and is not a clear duplicate.📝 Suggested next steps
exactpreservation.