Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the tspnamespace added to some of the types #1073

Closed
ArcturusZhang opened this issue Jun 25, 2024 · 0 comments · Fixed by #1075
Closed

Remove the tspnamespace added to some of the types #1073

ArcturusZhang opened this issue Jun 25, 2024 · 0 comments · Fixed by #1075
Assignees
Labels
lib:tcgc Issues for @azure-tools/typespec-client-generator-core library

Comments

@ArcturusZhang
Copy link
Member

We previously add the tspNamespace to identify exactly where this type was defined in the typespec file. But actually we are mislooking that there is already a property on model and enum to show that - the crossLanguageDefinitionId.
The downstream generator could use this value to know which typespec file the type is defined, which nullifies the purpose we add tspNamespace.

We might need to remove the tspNamespace property.

@ArcturusZhang ArcturusZhang added the lib:tcgc Issues for @azure-tools/typespec-client-generator-core library label Jun 25, 2024
github-merge-queue bot pushed a commit that referenced this issue Jun 26, 2024
…l, union and array types (#1075)

Fixes #1073

Per offline discussion, `crossLanguageDefinitionId` is actually a much
better candidate of telling people the originate of this type, therefore
this should solve all of our requirement and we no longer need a
`tspNamespace` anymore.

---------

Co-authored-by: Chenjie Shi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lib:tcgc Issues for @azure-tools/typespec-client-generator-core library
Projects
None yet
1 participant