SignalR returns PascalCase instead of camelCase

[JeanLoureiro]

Hi @larsmichael,

Can we please have the SignalR returning the object in camelCase?
This will make it consistent with the WebAPI format

Thank you.

cc: @FranzThomsen1089

[larsmichael]

Apparently this is not natively supported in AP.NET Core 2.2 which is the version we currently use. It can be done using this "hack". However, I am not very fond of this solution because of this comment:

So every time we resolve a contract in the ResolveContract method we have to check the assembly of the type currently resolved and check wether it is SignalR internal. If not, then we can resolve the contract using camel case.

Furthermore, it is very high on the general agenda to update to ASP.NET Core 5.0, where this is natively supported. Hopefully, we can make this upgrade within the coming months.

[goneale]

Hmm... I also returned my own C# POCO's with [JsonProperty("myName")] attribute attached, so I had full control at the other end. Can't this be the approach?

[larsmichael]

That is a path that i would not like to follow. Generally, we should have as few tech-specific attributes in the domain model objects as possible. Yes, they are already there, but should be kept at a minimum. This approach would require all properties of all domain model objects to be decorated with an attribute. Formatting of JSON-response is a web-concern rather than a domain model concern. Furthermore, we might switch to System.Text.Json instead of Newtonsoft.Json in future versions of the Web API (making the JsonProperty attribute obsolete)

[larsmichael]

I know that this is mostly a "battle" of who should take the pain of temporarily hacking a solution to this problem: frontend or backend. But in my opinion it must take precedence to keep the generic backend components as clean as possible.

[FranzThomsen1089]

Clean yes. But consistent as well. It will eventually become camecase this would just be a so that we avoid having many places that would suffer from a breaking change later. Because it will come in both json documents, jobs and time series.

[larsmichael]

The Web APIs are now updated to ASP.NET 5.0. So the solution is now as described here. Should I add this configuration of SignalR to the VS project templates?