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.

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

Jump to bottom

[FEATURE REQ] Make MultipartFormDataContent public #24819

Closed
Socolin opened this issue Oct 19, 2021 · 3 comments
Closed

[FEATURE REQ] Make MultipartFormDataContent public #24819

Socolin opened this issue Oct 19, 2021 · 3 comments
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Milestone
Backlog

Comments

@Socolin
Copy link

Socolin commented Oct 19, 2021 •
edited
Loading

Library or service name.
Azure.Core

Hello,

All your HttpPipeline stuff is great and so we are using them to build client for custom services too.
Could you expose MultipartFormDataContent by making it public instead of internal and expose _headers from MultipartContent (or maybe there is some code that should already read _headers and put it in the request headers that I missed) ?
@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Oct 19, 2021
@jsquire jsquire added Azure.Core Client This issue points to a problem in the data-plane of the library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team labels Oct 19, 2021
@jsquire
Copy link
Member

jsquire commented Oct 19, 2021

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

@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Oct 19, 2021
@pakrym pakrym added feature-request This issue requires a new behavior in the product in order be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Oct 26, 2021
@pakrym
Copy link
Contributor

pakrym commented Oct 27, 2021

We are definitely looking to move shared code APIs to public classes when they stabilize and get more widely used. Having said that it might take a while for this particular API.

@pakrym pakrym added this to the Backlog milestone Oct 27, 2021
@pakrym pakrym removed their assignment Jan 25, 2022
@annelo-msft annelo-msft mentioned this issue May 11, 2023
Closed
2 tasks
@annelo-msft
Copy link
Member

Tracking this request and the overall effort with #28369, so closing this instance.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@Socolin @jsquire @pakrym @annelo-msft