I noticed that the InstanceValidator class operates on JsonNode. Is there a particular architectural or functional reason for choosing JsonNode over JsonDocument?
My current implementation (C# app - .NET 10) uses JsonDocument due to EF Core’s native support. Converting between JsonDocument and JsonNode is relatively expensive and has a measurable impact on performance.
Would you consider adding native support for JsonDocument to avoid these conversions?
I noticed that the
InstanceValidatorclass operates onJsonNode. Is there a particular architectural or functional reason for choosingJsonNodeoverJsonDocument?My current implementation (C# app - .NET 10) uses
JsonDocumentdue to EF Core’s native support. Converting betweenJsonDocumentandJsonNodeis relatively expensive and has a measurable impact on performance.Would you consider adding native support for
JsonDocumentto avoid these conversions?