Namespace refactoring Scenario tests #758
Assignees
Comments
This was referenced Oct 23, 2024
This was referenced Nov 20, 2024
Closed
|
PR at initial review, for getting feedback from all languages. moved to typespec-azure repo |
github-merge-queue bot
pushed a commit
to Azure/typespec-azure
that referenced
this issue
Jan 9, 2025
fix Azure/cadl-ranch#758 move from Azure/cadl-ranch#775 This scenario mainly test the case when `@clientNamespace` applied to TypeSpec Namespace/Interface/Model/Enum. So far it does not test corner cases, like client/subclient in different namespace, name conflict for model in different namespace, etc. Current cases include 1. clients in different clientNamespace 2. client and model in different clientNamespace 3. model and the model of its property in different clientNamespace --------- Co-authored-by: Yuchao Yan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: