Add naming strategy support when post/put.. an object by url-encoded

[litliang-cn]

Is your feature request related to a problem? Please describe.

When calling Java's rest API (post/put.. an object by url-encoded), we have to add [AliasAs] attribute to each property of the class due to the difference of naming strategy (Java uses Camel, C-Sharp generally uses Pascal). It's a little silly.

Describe the solution you'd like

Can we increase the transformation of naming strategy (like newtonsoft. JSON), or provide an extension interface for us to implement the transformation from object to formdata?
Thanks!!

Describe alternatives you've considered

Maybe you can take 'BodySerializationMethod' as a parameter of 'IcontentSerializer.SerializeAsync' method, and then use newtonsoft.json to complete the transformation of naming strategy (convert object to JObject, and then traverse the properties of JObject)

Describe suggestions on how to achieve the feature

Additional context

[bennor]

Refit just uses Json.NET under the hood, so you can do this already. There's even an example in the README: https://github.com/reactiveui/refit#json-content

(Look for CamelCasePropertyNamesContractResolver.)

GitHub

reactiveui/refit

The automatic type-safe REST library for .NET Core, Xamarin and .NET. Heavily inspired by Square's Retrofit library, Refit turns your REST API into a live interface. - reactiveui/refit

[litliang-cn]

it does not wor when post form data（Body attribute was initialized with BodySerializationMethod.UrlEncoded） @bennor

[bennor]

Ah, apologies. I missed that part of the description.

[xljiulang]

Maybe only WebApiClient can help you!

services.AddHttpApi<IUserApi>(o =>
{
    // o.KeyValueSerializeOptions.PropertyNamingPolicy = null;
    o.KeyValueSerializeOptions.PropertyNamingPolicy = JsonNamingPolicy.CamelCase;
});