Skip to content

fix: required client init parameters should not trigger separate ClientOptions type #10375

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

Merged
JoshLove-msft merged 4 commits into from
Apr 17, 2026

fix: multi-service clients always use their own ClientOptions type

367bc44
Select commit
Loading
Failed to load commit list.
Merged

fix: required client init parameters should not trigger separate ClientOptions type #10375

fix: multi-service clients always use their own ClientOptions type
367bc44
Select commit
Loading
Failed to load commit list.
Azure Pipelines / typespec - ci (🔒 SDLSources 🔒 Agentless Tag) succeeded Apr 16, 2026

🔒 SDLSources 🔒 Agentless Tag succeeded

0 errors / 0 warnings

View more details on Azure Pipelines