-
Notifications
You must be signed in to change notification settings - Fork 75
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
Add client namespace and update test case #2994
base: main
Are you sure you want to change the base?
Conversation
…nto add-testcase19
…nto add-testcase19
import { OperationOptions } from '@azure-rest/core-client'; | ||
import { Pipeline } from '@azure/core-rest-pipeline'; | ||
|
||
export declare class ClientNamespaceFirstClient { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add the js decorator part in spector side? https://github.com/Azure/typespec-azure/pull/1929/files#r1953860516
- "@azure-tools/typespec-ts" | ||
options: | ||
"@azure-tools/typespec-ts": | ||
"emitter-output-dir": "{project-root}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you try if the namesapce is udpated after spec changed with option enableModelNamespace
and enableOperationGroup
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to update the spec first and then update our test config to verify this change.
fixes #3045