CosmosSerializationOptions to support other Newtonsoft options such as converters

[scottluskcis]

For the CosmosJsonDotNetSerializer it accepts a CosmosSerializationOptions object which then just gets mapped to Newtonsoft JsonSerializerSettings. This limits what we can do when want to do things such as using Custom JSON Converters because only the following properties are being used.

JsonSerializerSettings jsonSerializerSettings = new JsonSerializerSettings()
{
    NullValueHandling = cosmosSerializerOptions.IgnoreNullValues ? NullValueHandling.Ignore : NullValueHandling.Include,
    Formatting = cosmosSerializerOptions.Indented ? Formatting.Indented : Formatting.None,
    ContractResolver = cosmosSerializerOptions.PropertyNamingPolicy == CosmosPropertyNamingPolicy.CamelCase
        ? new CamelCasePropertyNamesContractResolver()
        : null
    };

Is there a reason why CosmosSerializationOptions doesn't support additional JsonSerializerSettings? Also the class is internal so prevents from any overrides of this behavior.

Can the class either be made public and be extended or can there be a way to support more JsonSerializerSettings, that would be a great help. Opening discussion on this to get any inputs. Thanks for your feedback!

[scottluskcis]

Adding link to existing issue that is related 1813

[j82w]

The reason is in the v4 SDK which will align with the Azure Core SDK guidelines requires the SDK to not take a dependency on Newtonsoft, but instead use the new more performant System.Text.Json. To make it an easier conversion from the v3 to v4 SDK it was decided to not directly expose any dependencies to Newtonsoft.

[gpuchtel]

Bump. What's the status of removing the dependency on Newtonsoft? In v3? (since I heard v4 is abandoned).

[church365]

Bump.

[Pilchie]

We can't remove the dependency on Newtonsoft within the v3 SDK - doing so would be a breaking change. Instead, we have been working on an option to allow the use of System.Text.Json instead. See #4332.