Dynamic properties not serialized camelCase when using Microsoft Json.NET package

[brgrz]

Describe the bug

This is essentially a duplicate of #9543

It was locked there but no resolution was provided and solutions/workarounds that used to work with ASP.NET MVC 5 do not work anymore in ASP.NET Core.

The default System.Text.Json serializer does not support dynamics at all. We had to revert to using Json.NET via Microsoft's Nuget package Microsoft.AspNetCore.Mvc.NewtonsoftJson (v. 3.1.12) to get support for dynamic serialization.

Then enabled it like this

			services
				.AddControllersWithViews()
				.AddNewtonsoftJson(options => options.UseCamelCasing(true));

Comments for UseCamelCasing() specifically say

Configures the casing behavior of JSON serialization to use camel case for property names, and optionally for dynamic types and dictionary keys.

and

If true will camel case dictionary keys and properties of dynamic objects.

This does not work though. Properties for dynamic objects within a typed object remain PascalCase when serialized.
I think this warrants a revisit to the issue I linked above and a possible resolution.

To Reproduce

Here is an example what comes out of a serializer when provided with a dynamic object within a typed object:

"records": [
        {
            "shape": null,
            "layout": "",
            "content": {
                "Location": null,
                "Address": null,
                "OpenHours": null,
                "Information": null,

Further technical details

• ASP.NET Core version: 3.1

[javiercn]

@brgrz thanks for contacting us.

@JamesNK is there something specific you need to setup to enable this in Newtonsoft.Json?

@brgrz WRT to dynamic support in System.Text.Json I would suggest you file an issue on the runtime repo so that they can track the ask.

[pranavkm]

@brgrz are you attempting to serialize a JObject? If so, according to #9543 (comment), Newtonsoft.Json will not transform the casing, so the behavior here is expected.

[brgrz]

It is a dynamic backed by a JObject, yes.

[ghost]

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!