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

[QUERY] design discussion on TypeSpec.Http.File and Azure.Core.FileWithRequiredMetadata #41769

Open
weidongxu-microsoft opened this issue Sep 10, 2024 · 1 comment
Assignees
Labels
Azure.Core azure-core Client This issue points to a problem in the data-plane of the library. DPG needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team

Comments

@weidongxu-microsoft
Copy link
Member

weidongxu-microsoft commented Sep 10, 2024

Link to typespec-azure Azure/typespec-azure#1458

When this merged, we will have 2 basic File model for multipart/form-data File, one in TypeSpec.Http, one in Azure.Core, with different requirement condition for the "filename" property (former is optional, latter is required).

Before we have corresponding class in Java azure-core (or clientcore), may I assume that they won't coexist on one typespec project, and I can map both to e.g. FileDetails class?

PS: probably a discussion with Srikanta

@github-actions github-actions bot added Azure.Core azure-core Client This issue points to a problem in the data-plane of the library. labels Sep 10, 2024
Copy link

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core azure-core Client This issue points to a problem in the data-plane of the library. DPG needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Projects
Status: No status
Development

No branches or pull requests

2 participants