-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Feature Request: Add various extension methods from Microsoft.AspNet.WebApi.Client #37055
Comments
Tagging subscribers to this area: @dotnet/ncl |
@pranavkm I don't think this should be transferred here, the functionality I'm looking for is mostly around very web-specific stuff regarding JSON. |
@pranavkm thanks, did not know that. The new APIs you linked to seem like they will cover a lot of my "wants" but I feel like it would be useful to cross-check them against what was/is available in |
@IanKemp can you please help with the cross check? Are there specific APIs which you think are missing? |
Triage: Does not seem to be critical for 5.0 -> Future. |
Unclear what is needed, closing. |
References:
aspnet/Mvc#1639
#16538
There is a NuGet package Microsoft.AspNet.WebApi.Client that provides a whole bunch of useful extension methods to allow you to perform various useful operations on
HttpClient
andHttpContent
instances (HttpContent.ReadAsAsync<T>()
andHttpClient.PostAsJsonAsync(string)
were my personal favourites). However that package is targeted at ye olde ASP.NET Web API 2, so I don't know how optimal it is for ASP.NET Core (e.g. it has no knowledge ofSpan<T>
) and/or how long it will continue to work with Core (especially since it was last updated over a year ago).Would it be desirable to add these extensions to ASP.NET Core? If not, is the
Microsoft.AspNet.WebApi.Client
package the correct and supported way to get those extensions going forward?The text was updated successfully, but these errors were encountered: