-
Notifications
You must be signed in to change notification settings - Fork 276
Allow to change serialization naming policy #209
Comments
@Jluil is the suggestion to make JsonNamingPolicy.CamelCase the default globally or allow to make it configurable? Not sure we can force a default globally the way we are setup currently. I have not looked closely, there may be a way. Just FYI the next version of Chromely will use Microsoft.Extensions.DependencyInjection. I have looked at it closely and it seems light enough for Chromely. So this will replace - Caliburn.Light Container. So with this, change should be easy for developers to make. We just need to create bandwidth for that. Good point! 👍 |
Hey, thanks for the response. |
@Jluil by Utility class, you mean int the Extension method? Sure, that can be improved. Thanks for pointing it out.
This needs to be thought through. The use of System.Text.Json is more of a suggestive use rather than a standard. Chromely more or less uses it in default classes. Those classes are replaceable and customizable. So in essence the serializing library can be replaced. Developers are not necessarily tied to System.Text.Json. They can use any serializing library. Like I mentioned earlier, we will see how all these fit in when we move to Microsoft.Extensions.DependencyInjection. Suggestions are always welcome. Thanks. |
It's really nice that .NET has it's own Json serializer that can do stuff like PascalCase to camelCase conversion by simply changing: PropertyNamingPolicy = JsonNamingPolicy.CamelCase. |
For Newtonsoft.JSON this could be
|
Allow to change serialization naming policy to JsonNamingPolicy.CamelCase.
This behavior is now standard for .NET core services, where .NET has PascalCase properties and client web app uses CamelCase properties.
The text was updated successfully, but these errors were encountered: