[FEATURE REQ] consider making Azure.Core.Utf8RequestContent public

[cataggar]

Library name

Azure.Core

Please describe the feature.

In March, Utf8JsonRequestContent.cs was duplicated many many times in this PR because it is internal in Azure.Core. Before this PR, it was in the Autorest shared code. I too need to duplicate it in our internal code. Please consider making it public.

Related issues:

• [FEATURE REQ] Improve the performance of Utf8JsonRequestContent and GZipUtf8JsonRequestContent. #30714
• System.Net.ClientModel and Azure.Core client building blocks #39023

[jsquire]

Hi @cataggar. Thanks for reaching out and for your suggestion. We'll take this under advisement and provide an update when a decision has been reached.

[jsquire]

//cc: @annelo-msft

[annelo-msft]

@cataggar - yes. We are tracking the migration of shared source types to public types with #43760. This specific one will likely look different as we proceed with that migration work as we now have a content-writing story centered around the ModelReaderWriter types in System.ClientModel. Thanks for flagging this one and keep an eye on that issue to track progress in this space. Thanks!

[annelo-msft]

@cataggar, would you be willing to share the specific use case you have that motivates your need for this feature? Thanks!

[github-actions]

Hi @cataggar. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[github-actions]

Hi @cataggar, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

[cataggar]

I'll be upgrading our internal client in November, so I expect to get back to this then.

[cataggar]

I'm working on this internal pull request.. After some digging, it looks like my primary use case for Utf8RequestContent is a workaround for:

• string request content not encoded as json autorest.csharp#3667

I'm going to check to see if I can remove the workaround now that it is fixed with:

• support json payload which is not object or array autorest.csharp#3733