Use of JsonConvert.DefaultSettings breaks unrelated serialization in v1.4

[seancolonello]

Upgrading from version 1.3.0 to 1.4.0 resulted in breaking changes for other aspects of my project. The project uses JsonConvert.SerializeObject() with default settings, which retains the POCO property casing (PascalCase in my situation). After the 1.4 update JsonConvert.SerializeObject() defaults to camelCase. This is running locally via Visual Studio 2019, I'm not sure if the same behavior exists deployed to Azure infrastructure.

I assume it's due to the following code fragment in SignalRConfigProvider.Initialize(), which is marked [Obsolete("preview")].

azure-functions-signalrservice-extension/src/SignalRServiceExtension/Config/SignalRConfigProvider.cs

Lines 68 to 75 in dbe3704

	JsonConvert.DefaultSettings = () => new JsonSerializerSettings()
	{
	Converters = new List<JsonConverter>() { new ServiceEndpointJsonConverter() },
	ContractResolver = new DefaultContractResolver
	{
	NamingStrategy = new CamelCaseNamingStrategy()
	}
	};

I'd say it's bad practice to set global serialization defaults in a library like this, that should be reserved for top level applications. Custom JsonSerializerSettings should be passed via the appropriate overload to JsonConvert methods.

[Y-Sindo]

Thanks for your feedback. We will consider improve it.