[tcgc]: add exact() function for preserving client names without …#4378
Open
iscai-msft wants to merge 5 commits intoAzure:mainfrom
Open
[tcgc]: add exact() function for preserving client names without …#4378iscai-msft wants to merge 5 commits intoAzure:mainfrom
exact() function for preserving client names without …#4378iscai-msft wants to merge 5 commits intoAzure:mainfrom
Conversation
…casing transformations
Add the exact() function that can be used with @clientName to signal
that language emitters should not apply their usual casing transformations
(e.g., snake_case for Python, PascalCase for C#).
Usage: @clientName(exact("hello_world"), "python")
Implementation:
- extern fn exact() in lib/functions.tsp that returns a prefixed string
- normalizeExactName/hasExactNameMarker helpers for stripping the prefix
- isExactName field added to SDK interfaces (SdkModelType, SdkEnumType,
SdkUnionType, SdkConstantType, SdkNullableType, SdkModelPropertyTypeBase,
SdkClientInitializationType)
- isExactClientName() public utility for checking exact name status
- Prefix is stripped at name resolution time (getLibraryName) and
isExactName is set at SDK type creation time
- 7 new tests covering models, properties, enums, operations, and
language-scoped exact names
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
iscai-msft
requested review from
bterlson,
joheredi,
lmazuel,
m-nash,
markcowl,
srnagar and
timotheeguerin
as code owners
The `exact()` function preserves client names without language-specific casing transformations. Added `isExactName` field to SDK type interfaces for emitters to check casing transformations.
microsoft-github-policy-service
Bot
added
the
lib:tcgc
Contributor
⚡ Benchmark ResultsComparing [
|
Collaborator
|
All changed packages have been documented.
Show changes
|
commit: |
Collaborator
|
You can try these changes here
|
added 2 commits
May 5, 2026 13:45
…scai-msft/typespec-azure into feature/tcgc-exact-client-name
timotheeguerin
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…casing transformations
Add the exact() function that can be used with @clientName to signal that language emitters should not apply their usual casing transformations (e.g., snake_case for Python, PascalCase for C#).
Usage: @clientName(exact("hello_world"), "python")
Implementation: