Bitbucket.Net changes default JSON serialization settings

[jhonny-apiiro]

this static ctor changes the default JSON serialization settings in the application.
I think this is a problem, since other code may rely on the "default" set of defaults.
I don't expect a library to change the global settings in my application..

For example, in the application I'm working on now, we have many integrations with many 3rd party APIs.
I spent more time than I would've liked trying to figure out why an integration with service X was working as expected normally, but not working only on certain servers / certain customers.
turns out that, as long as the bitbucket integration wasn't turned on, everything was great. but once we turned on integration for bitbucket AND service X, service X stopped working as expected.
that's because Bitbucket.NET changed how the requests to service X were serialized!

[diomonogatari]

Hey there,
I've forked this project because it's essentially unmaintained because I wanted to modernize it for my needs.

This issue is resolved in the modernized fork. The problematic static constructor that sets JsonConvert.DefaultSettings has been removed.

The updated implementation:

• Uses System.Text.Json instead of Newtonsoft.Json
• Scopes serialization settings to the BitbucketClient instance only
• No longer mutates global JSON defaults

Available now: BitbucketServer.Net v0.2.0 on NuGet

Repository: https://github.com/diomonogatari/Bitbucket.Net

I know your issue has some years already but maybe it's still relevant for you.
Cheers,