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

ClientInitialization/ParamAlias Implementation #2894

Open
Tracked by #1768
lmazuel opened this issue Oct 30, 2024 · 5 comments
Open
Tracked by #1768

ClientInitialization/ParamAlias Implementation #2894

lmazuel opened this issue Oct 30, 2024 · 5 comments
Assignees

Comments

@lmazuel
Copy link
Member

lmazuel commented Oct 30, 2024

No description provided.

@iscai-msft
Copy link
Contributor

implemented

@msyyc
Copy link
Member

msyyc commented Nov 4, 2024

implemented

@iscai-msft Could you share the PR link? I don't find any PR to implement this feature.

@msyyc msyyc reopened this Nov 4, 2024
@iscai-msft
Copy link
Contributor

There isn't any need for us to do anything on the autorest.python side, it's all handled by tcgc

@msyyc
Copy link
Member

msyyc commented Nov 6, 2024

There isn't any need for us to do anything on the autorest.python side, it's all handled by tcgc

Here is cadl-ranch case https://github.com/Azure/cadl-ranch/pull/727/files for this scenario, and I try to generate Python SDK locally https://github.com/Azure/autorest.python/tree/sample-2024-11-06/packages/typespec-python/tsp-output/%40azure-tools/typespec-python. Then I find "name" is not exposed as client signature:
Image
Image

@iscai-msft
Copy link
Contributor

hmm ok, i guess it does deserve another look, thanks for following up on this issue @msyyc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants