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.

Sign up for GitHub

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

Jump to bottom

Singleton resource do not work with separate client namespace #1374

Open
timotheeguerin opened this issue Aug 14, 2024 · 0 comments
Open

Singleton resource do not work with separate client namespace #1374

timotheeguerin opened this issue Aug 14, 2024 · 0 comments
Labels
bug Something isn't working lib:azure-resource-manager Issues for @azure-tools/typespec-azure-core library triaged:core
Milestone
[2024] October

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.
@timotheeguerin timotheeguerin added bug Something isn't working lib:azure-resource-manager Issues for @azure-tools/typespec-azure-core library labels Aug 14, 2024
@markcowl markcowl added this to the [2024] October milestone Aug 21, 2024
@timotheeguerin timotheeguerin mentioned this issue Aug 29, 2024
Closed
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working lib:azure-resource-manager Issues for @azure-tools/typespec-azure-core library triaged:core
Projects
None yet
Milestone
[2024] October
Development

No branches or pull requests
2 participants
@timotheeguerin @markcowl