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

Singleton resource do not work with separate client namespace #1374

Closed
timotheeguerin opened this issue Aug 14, 2024 · 1 comment
Closed
Labels
bug Something isn't working lib:azure-resource-manager Issues for @azure-tools/typespec-azure-core library triaged:core

Comments

@timotheeguerin
Copy link
Member

See the openapi3 emitter for client then route use {employeeName} instead of default

Playground Link

The problem is that we set this route resolution option on the namespace which is then not resolved in the client namespace.

@weidongxu-microsoft
Copy link
Member

weidongxu-microsoft commented Dec 5, 2024

Currently, this is the last remaining blocker for SDK team to generate SDK directly from TypeSpec, for a relatively large brownfield (avs) service that already done the conversion to TypeSpec (and verified the result via Swagger and TypeSpec).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working lib:azure-resource-manager Issues for @azure-tools/typespec-azure-core library triaged:core
Projects
None yet
Development

No branches or pull requests

5 participants