Open Daniel15 opened 5 years ago
@caleblloyd Is there any particular reason for putting JsonObject
in the System
namespace?
Really just legacy reasons. Changing it would be a BC Break
NPGSQL has JSON support now and they use an interesting approach:
https://www.npgsql.org/efcore/mapping/json.html
Amongst other options, they use the .NET Core 3.0 System.Text.Json
APIs
https://devblogs.microsoft.com/dotnet/try-the-new-system-text-json-apis/
Aligning seems like a logical course if we were to break BC anyways
Why is
JsonObject
in theSystem
namespace? That's very confusing because it makes it seem like this is part of the .NET framework (rather than a third-party package), and there's also aJsonObject
class in theSystem.Json
namespace (https://docs.microsoft.com/en-us/dotnet/api/system.json.jsonobject?view=dotnet-plat-ext-2.1). Could you please consider moving it to aPomelo.JsonObject
namespace?