Skip to content

Conversation

@msyyc
Copy link
Contributor

@msyyc msyyc commented Jan 23, 2025

We shall keep compatibility for scenario that output folder is different with namespace (e.g. azure-communication-callautomation has additional _generated in output folder which is not in namespace)

@microsoft-github-policy-service microsoft-github-policy-service bot added the emitter:client:python Issue for the Python client emitter: @typespec/http-client-python label Jan 23, 2025
@azure-sdk
Copy link
Collaborator

No changes needing a change description found.

@azure-sdk
Copy link
Collaborator

azure-sdk commented Jan 23, 2025

You can try these changes here

🛝 Playground 🌐 Website 📚 Next docs 🛝 VSCode Extension

@msyyc msyyc changed the title [python] Fix for scenario that output folder is different with namespace [python] Fix for scenario that output folder is different with namespace (pending on adding test cases) Jan 23, 2025
@msyyc msyyc changed the title [python] Fix for scenario that output folder is different with namespace (pending on adding test cases) [python] Fix for scenario that output folder is different with namespace Jan 23, 2025
@iscai-msft iscai-msft added this pull request to the merge queue Jan 23, 2025
Merged via the queue into main with commit 3210f18 Jan 23, 2025
26 checks passed
@iscai-msft iscai-msft deleted the fix-namespace branch January 23, 2025 16:53
github-merge-queue bot pushed a commit that referenced this pull request Jan 24, 2025
…with namespace in configuration (#5739)

Supplementation for #5711. The
issue is not covered by test case since test case doesn't contain
`models`. Here is updated test case to cover this issue:
https://github.com/Azure/autorest.python/pull/3030/files#diff-5fa7ea68bc2d31e09e995e5f522a9e4f58572767f393937a1cf6baf35fa16664
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

emitter:client:python Issue for the Python client emitter: @typespec/http-client-python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants