Skip to content

Extend multiple-services design doc with nested @client pattern for client hierarchy customization #3847

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

Open
Copilot wants to merge 19 commits into
base: main
Choose a base branch
from
+697 −3
Open

Extend multiple-services design doc with nested @client pattern for client hierarchy customization #3847

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
9dbda1e
Initial plan
Copilot Jan 27, 2026
98b33de
Update multiple-services.md design doc with extended client hierarchy…
Copilot Jan 27, 2026
cb08ae3
Address code review comments on design doc
Copilot Jan 27, 2026
b39f412
Fix inconsistency in validation rules section
Copilot Jan 27, 2026
f20ed7f
Refine design to remove autoMerge flag, use nested @client pattern in…
Copilot Jan 28, 2026
30c01d2
Fix minor wording and clarity issues from code review
Copilot Jan 28, 2026
83e9199
Address PR review comments: add Python examples, add clientInitializa…
Copilot Jan 28, 2026
b837d38
Add 2D apiVersions and endpoint/credential limitations documentation
Copilot Jan 28, 2026
c0e3cd3
Expand Changes Needed section with detailed implementation requirements
Copilot Jan 28, 2026
f1d6c4c
Merge branch 'main' into copilot/update-client-hierarchy-design
tadelesh Jan 28, 2026
c4d9bce
Format the design doc with prettier
Copilot Jan 28, 2026
eaab34a
format
Jan 29, 2026
c0517f2
Replace 2D apiVersions array with apiVersionsMap for cross-service cl…
Copilot Jan 30, 2026
448799a
Update design: multiple @service namespaces create separate root clie…
Copilot Jan 30, 2026
59382d3
Add Scenario 0 for default multiple services behavior with full YAML …
Copilot Jan 30, 2026
e613f9b
format
Jan 30, 2026
af1d378
Add Scenario 1.5 for mixing multi-service and single-service clients
Copilot Feb 2, 2026
1c7e6f2
Clarify that only services in the service array are included in client
Copilot Feb 2, 2026
ce258e0
Add service property to all nested @client decorators in Scenario 3
Copilot Feb 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/typespec-client-generator-core/design-docs/client.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ sub_client.do_something()

The entrance of TCGC is `SdkPackage` which represents a complete package and includes clients, models, etc. The clients depend on the combination usage of namespace, interface, `@service`, `@client`.

If there is no explicitly defined `@client`, then the first namespaces with `@service` will be a client. The nested namespaces and interfaces under that namespace will be a sub client with hierarchy.
If there is no explicitly defined `@client`, then each namespace with `@service` will be a separate root client. The nested namespaces and interfaces under each service namespace will be sub clients with hierarchy.

- Example 1:

Expand Down
Loading