{"id":1333,"date":"2024-10-15T16:22:19","date_gmt":"2024-10-15T16:22:19","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2024\/10\/15\/whats-new-in-system-text-json-in-net-9\/"},"modified":"2024-10-15T16:22:19","modified_gmt":"2024-10-15T16:22:19","slug":"whats-new-in-system-text-json-in-net-9","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2024\/10\/15\/whats-new-in-system-text-json-in-net-9\/","title":{"rendered":"What\u2019s new in System.Text.Json in .NET 9"},"content":{"rendered":"

The 9.0 release of System.Text.Json includes many features, primarily with a focus on JSON schema and intelligent application support. It also includes highly requested enhancements such as nullable reference type support, customizing enum member names, out-of-order metadata deserialization and customizing serialization indentation.<\/p>\n

Getting the latest bits<\/h3>\n

You can try out the new features by referencing the latest build of System.Text.Json NuGet package<\/a> or the latest SDK for .NET 9<\/a>.<\/p>\n

JSON Schema Exporter<\/h2>\n

The new JsonSchemaExporter class can be used to extract JSON schema<\/a> documents from .NET types using either JsonSerializerOptions or JsonTypeInfo instances:<\/p>\n

using System.Text.Json.Schema;<\/p>\n

JsonSerializerOptions options = JsonSerializerOptions.Default;
\nJsonNode schema = options.GetJsonSchemaAsNode(typeof(Person));
\nConsole.WriteLine(schema.ToString());
\n\/\/{
\n\/\/ “type”: [“object”, “null”],
\n\/\/ “properties”: {
\n\/\/ “Name”: { “type”: “string” },
\n\/\/ “Age”: { “type”: “integer” },
\n\/\/ “Address”: { “type”: [“string”, “null”], “default”: null }
\n\/\/ },
\n\/\/ “required”: [“Name”, “Age”]
\n\/\/}<\/p>\n

record Person(string Name, int Age, string? Address = null);<\/p>\n

The resultant schema provides a specification of the JSON serialization contract for the type. As can be seen in this example, it distinguishes between nullable and non-nullable properties and populates the required keyword by virtue of a constructor parameter being optional or not. The schema output can be influenced by configuration specified in the JsonSerializerOptions or JsonTypeInfo instances:<\/p>\n

JsonSerializerOptions options = new(JsonSerializerOptions.Default)
\n{
\n PropertyNamingPolicy = JsonNamingPolicy.KebabCaseUpper,
\n NumberHandling = JsonNumberHandling.WriteAsString,
\n UnmappedMemberHandling = JsonUnmappedMemberHandling.Disallow,
\n};<\/p>\n

JsonNode schema = options.GetJsonSchemaAsNode(typeof(MyPoco));
\nConsole.WriteLine(schema.ToString());
\n\/\/{
\n\/\/ “type”: [“object”, “null”],
\n\/\/ “properties”: {
\n\/\/ “NUMERIC-VALUE”: {
\n\/\/ “type”: [“string”, “integer”],
\n\/\/ “pattern”: “^-?(?:0|[1-9]\\d*)$”
\n\/\/ }
\n\/\/ },
\n\/\/ “additionalProperties”: false
\n\/\/}<\/p>\n

class MyPoco
\n{
\n public int NumericValue { get; init; }
\n}<\/p>\n

The generated schema can be further controlled using the JsonSchemaExporterOptions configuration type:<\/p>\n

JsonSerializerOptions options = JsonSerializerOptions.Default;
\nJsonSchemaExporterOptions exporterOptions = new()
\n{
\n \/\/ Marks root-level types as non-nullable
\n TreatNullObliviousAsNonNullable = true,
\n};<\/p>\n

JsonNode schema = options.GetJsonSchemaAsNode(typeof(Person), exporterOptions);
\nConsole.WriteLine(schema.ToString());
\n\/\/{
\n\/\/ “type”: “object”,
\n\/\/ “properties”: {
\n\/\/ “Name”: { “type”: “string” }
\n\/\/ },
\n\/\/ “required”: [“Name”]
\n\/\/}<\/p>\n

record Person(string Name);<\/p>\n

Finally, users are able to apply their own transformations to generated schema nodes by specifying a TransformSchemaNode delegate. Here\u2019s an example that incorporates text from DescriptionAttribute annotations:<\/p>\n

JsonSchemaExporterOptions exporterOptions = new()
\n{
\n TransformSchemaNode = (context, schema) =>
\n {
\n \/\/ Determine if a type or property and extract the relevant attribute provider
\n ICustomAttributeProvider? attributeProvider = context.PropertyInfo is not null
\n ? context.PropertyInfo.AttributeProvider
\n : context.TypeInfo.Type;<\/p>\n

\/\/ Look up any description attributes
\n DescriptionAttribute? descriptionAttr = attributeProvider?
\n .GetCustomAttributes(inherit: true)
\n .Select(attr => attr as DescriptionAttribute)
\n .FirstOrDefault(attr => attr is not null);<\/p>\n

\/\/ Apply description attribute to the generated schema
\n if (descriptionAttr != null)
\n {
\n if (schema is not JsonObject jObj)
\n {
\n \/\/ Handle the case where the schema is a boolean
\n JsonValueKind valueKind = schema.GetValueKind();
\n Debug.Assert(valueKind is JsonValueKind.True or JsonValueKind.False);
\n schema = jObj = new JsonObject();
\n if (valueKind is JsonValueKind.False)
\n {
\n jObj.Add(“not”, true);
\n }
\n }<\/p>\n

jObj.Insert(0, “description”, descriptionAttr.Description);
\n }<\/p>\n

return schema;
\n }
\n};<\/p>\n

Tying it all together, we can now generate a schema that incorporates description keyword source from attribute annotations:<\/p>\n

JsonNode schema = options.GetJsonSchemaAsNode(typeof(Person), exporterOptions);
\nConsole.WriteLine(schema.ToString());
\n\/\/{
\n\/\/ “description”: “A person”,
\n\/\/ “type”: [“object”, “null”],
\n\/\/ “properties”: {
\n\/\/ “Name”: { “description”: “The name of the person”, “type”: “string” }
\n\/\/ },
\n\/\/ “required”: [“Name”]
\n\/\/}<\/p>\n

[Description(“A person”)]
\nrecord Person([property: Description(“The name of the person”)] string Name);<\/p>\n

This is a particularly useful component when it comes to generating schemas for .NET methods or APIs; it is being used to power ASP.NET Core\u2019s newly released OpenAPI component and we\u2019ve deployed it to a number of AI related libraries and applications with tool calling requirements such as Semantic Kernel, Visual Studio Copilot and the the newly released Microsoft.Extensions.AI library.<\/p>\n

Streaming multiple JSON documents<\/h2>\n

Utf8JsonReader now supports reading multiple, whitespace-separated JSON documents from a single buffer or stream. By default, Utf8JsonReader will throw an exception if it detects any non-whitespace characters that are trailing the first top-level document. This behavior can be changed using the JsonReaderOptions.AllowMultipleValues flag:<\/p>\n

JsonReaderOptions options = new() { AllowMultipleValues = true };
\nUtf8JsonReader reader = new(“null {} 1 rn [1,2,3]”u8, options);<\/p>\n

reader.Read();
\nConsole.WriteLine(reader.TokenType); \/\/ Null<\/p>\n

reader.Read();
\nConsole.WriteLine(reader.TokenType); \/\/ StartObject
\nreader.Skip();<\/p>\n

reader.Read();
\nConsole.WriteLine(reader.TokenType); \/\/ Number<\/p>\n

reader.Read();
\nConsole.WriteLine(reader.TokenType); \/\/ StartArray
\nreader.Skip();<\/p>\n

Console.WriteLine(reader.Read()); \/\/ False<\/p>\n

This additionally makes it possible to read JSON from payloads that may contain trailing data that is invalid JSON:<\/p>\n

Utf8JsonReader reader = new(“[1,2,3] <NotJson\/>”u8, new() { AllowMultipleValues = true });<\/p>\n

reader.Read();
\nreader.Skip(); \/\/ Success
\nreader.Read(); \/\/ throws JsonReaderException<\/p>\n

When it comes to streaming deserialization, we have included a new JsonSerializer.DeserializeAsyncEnumerable overload that makes streaming multiple top-level values possible. By default, DeserializeAsyncEnumerable will attempt to stream elements that are contained in a top-level JSON array. This behavior can be toggled using the new topLevelValues flag:<\/p>\n

ReadOnlySpan<byte> utf8Json = “””[0] [0,1] [0,1,1] [0,1,1,2] [0,1,1,2,3]”””u8;
\nusing var stream = new MemoryStream(utf8Json.ToArray());<\/p>\n

await foreach (int[] item in JsonSerializer.DeserializeAsyncEnumerable<int[]>(stream, topLevelValues: true))
\n{
\n Console.WriteLine(item.Length);
\n}<\/p>\n

Respecting nullable annotations<\/h2>\n

JsonSerializer now adds limited support for non-nullable reference type enforcement in serialization and deserialization. This can be toggled using the RespectNullableAnnotations flag:<\/p>\n

#nullable enable
\nJsonSerializerOptions options = new() { RespectNullableAnnotations = true };<\/p>\n

MyPoco invalidValue = new(Name: null!);
\nJsonSerializer.Serialize(invalidValue, options);
\n\/\/ System.Text.Json.JsonException: The property or field ‘Name’
\n\/\/ on type ‘MyPoco’ doesn’t allow getting null values. Consider
\n\/\/ updating its nullability annotation. <\/p>\n

record MyPoco(string Name);<\/p>\n

Similarly, this setting adds enforcement on deserialization:<\/p>\n

JsonSerializerOptions options = new() { RespectNullableAnnotations = true };
\nstring json = “””{“Name”:null}”””;
\nJsonSerializer.Deserialize<MyPoco>(json, options);
\n\/\/ System.Text.Json.JsonException: The constructor parameter ‘Name’
\n\/\/ on type ‘MyPoco’ doesn’t allow null values. Consider updating
\n\/\/ its nullability annotation.<\/p>\n

Limitations<\/h3>\n

Due to how non-nullable reference types are implemented, this feature comes with an important number of limitations that users need to familiarize themselves with before turning it on. The root of the issue is that reference type nullability has no first-class representation in IL, as such the expressions MyPoco and MyPoco? are indistinguishable from the perspective of run-time reflection<\/a>. While the compiler will try to make up for that by emitting attribute metadata where possible<\/a>, this is restricted to non-generic member annotations that are scoped to a particular type definition. It is for this reason that the flag only validates nullability annotations that are present on non-generic properties, fields, and constructor parameters. System.Text.Json does not support nullability enforcement on<\/p>\n

Top-level types, aka the type that is passed when making the first JsonSerializer.(De)serialize call.
\nCollection element types, aka we cannot distinguish between List<string> and List<string?> types.
\nAny properties, fields, or constructor parameters that are generic.<\/p>\n

If you are looking to add nullability enforcement in these cases, we recommend that you either model your type to be a struct (since they do not admit null values) or author a custom converter that overrides its HandleNull<\/a> property to true.<\/p>\n

Feature switch<\/h3>\n

Users can turn on the RespectNullableAnnotations setting globally using the System.Text.Json.Serialization.RespectNullableAnnotationsDefault feature switch, which can be set via your project configuration:<\/p>\n

<ItemGroup>
\n <RuntimeHostConfigurationOption Include=”System.Text.Json.Serialization.RespectNullableAnnotationsDefault” Value=”true” \/>
\n<\/ItemGroup><\/p>\n

On the relation between nullable and optional parameters<\/h3>\n

It should be noted that RespectNullableAnnotations does not extend enforcement to unspecified JSON values:<\/p>\n

JsonSerializerOptions options = new() { RespectNullableAnnotations = true };
\nvar result = JsonSerializer.Deserialize<MyPoco>(“{}”, options); \/\/ No exception!
\nConsole.WriteLine(result.Name is null); \/\/ True<\/p>\n

class MyPoco
\n{
\n public string Name { get; set; }
\n}<\/p>\n

This is because STJ treats required and non-nullable properties as orthogonal concepts. This stems from the C# language itself where you can have required properties that are nullable:<\/p>\n

MyPoco poco = new() { Value = null }; \/\/ No compiler warnings<\/p>\n

class MyPoco
\n{
\n public required string? Value { get; set; }
\n}<\/p>\n

And optional properties that are non-nullable:<\/p>\n

class MyPoco
\n{
\n public string Value { get; set; } = “default”;
\n}<\/p>\n

The same orthogonality applies to constructor parameters:<\/p>\n

record MyPoco(
\n string RequiredNonNullable,
\n string? RequiredNullable,
\n string OptionalNonNullable = “default”,
\n string? OptionalNullable = “default”);<\/p>\n

Respecting non-optional constructor parameters<\/h2>\n

STJ constructor-based deserialization has historically been treating all constructor parameters as optional, as can be highlighted in the following example:<\/p>\n

var result = JsonSerializer.Deserialize<Person>(“{}”);
\nConsole.WriteLine(result); \/\/ Person { Name = , Age = 0 }<\/p>\n

record Person(string Name, int Age);<\/p>\n

In .NET 9 we\u2019re including the RespectRequiredConstructorParameters flag that changes the behavior such that non-optional constructor parameters are now treated as required:<\/p>\n

JsonSerializerOptions options = new() { RespectRequiredConstructorParameters = true };
\nstring json = “””{“Optional”: “value”}”””;
\nJsonSerializer.Deserialize<MyPoco>(json, options);<\/p>\n

record MyPoco(string Required, string? Optional = null);
\n\/\/ JsonException: JSON deserialization for type ‘MyPoco’
\n\/\/ was missing required properties including: ‘Required’.<\/p>\n

Feature switch<\/h3>\n

Users can turn on the RespectRequiredConstructorParameters setting globally using the System.Text.Json.Serialization.RespectRequiredConstructorParametersDefault feature switch, which can be set via your project configuration:<\/p>\n

<ItemGroup>
\n <RuntimeHostConfigurationOption Include=”System.Text.Json.Serialization.RespectRequiredConstructorParametersDefault” Value=”true” \/>
\n<\/ItemGroup><\/p>\n

Both the RespectNullableAnnotations and RespectRequiredConstructorParameter properties were implemented as opt-in flags to avoid breaking existing applications. If you\u2019re writing a new application, it is highly recommended that you enable both flags in your code.<\/p>\n

Customizing enum member names<\/h2>\n

The new JsonStringEnumMemberName attribute can be used to customize the names of individual enum members for types that are serialized as strings:<\/p>\n

JsonSerializer.Serialize(MyEnum.Value1 | MyEnum.Value2); \/\/ “Value1, Custom enum value”<\/p>\n

[Flags, JsonConverter(typeof(JsonStringEnumConverter))]
\nenum MyEnum
\n{
\n Value1 = 1,
\n [JsonStringEnumMemberName(“Custom enum value”)]
\n Value2 = 2,
\n}<\/p>\n

Out-of-order metadata reads<\/h2>\n

Certain features of System.Text.Json such as polymorphism or ReferenceHandler.Preserve require emitting metadata properties over the wire:<\/p>\n

JsonSerializerOptions options = new() { ReferenceHandler = ReferenceHandler.Preserve };
\nBase value = new Derived(“Name”);
\nJsonSerializer.Serialize(value, options); \/\/ {“$id”:”1″,”$type”:”derived”,”Name”:”Name”}<\/p>\n

[JsonDerivedType(typeof(Derived), “derived”)]
\nrecord Base;
\nrecord Derived(string Name) : Base;<\/p>\n

By default, the STJ metadata reader requires that the metadata properties $id and $type must be defined at the start of the JSON object:<\/p>\n

JsonSerializer.Deserialize<Base>(“””{“Name”:”Name”,”$type”:”derived”}”””);
\n\/\/ JsonException: The metadata property is either not supported by the
\n\/\/ type or is not the first property in the deserialized JSON object.<\/p>\n

This is known to create problems when needing to deserialize JSON payloads that do not originate from System.Text.Json. The new AllowOutOfOrderMetadataProperties can be configured to disable this restriction:<\/p>\n

JsonSerializerOptions options = new() { AllowOutOfOrderMetadataProperties = true };
\nJsonSerializer.Deserialize<Base>(“””{“Name”:”Name”,”$type”:”derived”}”””, options); \/\/ Success<\/p>\n

Care should be taken when enabling this flag, as it might result in over-buffering (and OOM failures) when performing streaming deserialization of very large JSON objects. This is because metadata properties must be read before<\/em> the deserialize object is instantiated, meaning that all properties preceding a $type property must be kept in the buffer for subsequent property binding.<\/p>\n

Customizing indentation<\/h2>\n

The JsonWriterOptions and JsonSerializerOptions types now expose APIs for configuring indentation. The following example enables single-tab indentation:<\/p>\n

JsonSerializerOptions options = new()
\n{
\n WriteIndented = true,
\n IndentCharacter = ‘t’,
\n IndentSize = 1,
\n};<\/p>\n

JsonSerializer.Serialize(new { Value = 42 }, options);<\/p>\n

JsonObject property order manipulation<\/h2>\n

The JsonObject type is part of the mutable DOM and is used to represent JSON objects. Even though the type is modelled as an IDictionary<string, JsonNode>, it does encapsulate an implicit property order that is not user-modifiable. The new release exposes additional APIs that effectively model the type as an ordered dictionary:<\/p>\n

public partial class JsonObject : IList<KeyValuePair<string, JsonNode?>>
\n{
\n public int IndexOf(string key);
\n public void Insert(int index, string key, JsonNode? value);
\n public void RemoveAt(int index);
\n}<\/p>\n

This allows modifications to object instances that can directly influence property order:<\/p>\n

\/\/ Adds or moves the $id property to the start of the object
\nvar schema = (JsonObject)JsonSerializerOptions.Default.GetJsonSchemaAsNode(typeof(MyPoco));
\nswitch (schema.IndexOf(“$id”, out JsonNode? idValue))
\n{
\n case < 0: \/\/ $id property missing
\n idValue = (JsonNode)”https:\/\/example.com\/schema”;
\n schema.Insert(0, “$id”, idValue);
\n break;<\/p>\n

case 0: \/\/ $id property already at the start of the object
\n break; <\/p>\n

case int index: \/\/ $id exists but not at the start of the object
\n schema.RemoveAt(index);
\n schema.Insert(0, “$id”, idValue);
\n}<\/p>\n

DeepEquals methods in JsonElement and JsonNode<\/h2>\n

The new JsonElement.DeepEquals method extends deep equality comparison to JsonElement instances, complementing the pre-existing JsonNode.DeepEquals method. Additionally, both methods include refinements in their implementation, such as handling of equivalent JSON numeric representations:<\/p>\n

JsonElement left = JsonDocument.Parse(“10e-3”).RootElement;
\nJsonElement right = JsonDocument.Parse(“0.01”).RootElement;
\nJsonElement.DeepEquals(left, right); \/\/ True<\/p>\n

JsonSerializerOptions.Web<\/h2>\n

The new JsonSerializerOptions.Web singleton can be used to quickly serialize values using JsonSerializerDefaults.Web settings:<\/p>\n

JsonSerializerOptions options = JsonSerializerOptions.Web; \/\/ used instead of new(JsonSerializerDefaults.Web);
\nJsonSerializer.Serialize(new { Value = 42 }, options); \/\/ {“value”:42}<\/p>\n

Performance improvements<\/h2>\n

For a detailed write-up of System.Text.Json performance improvements in .NET 9, please refer to the relevant section<\/a> in Stephen Toub\u2019s \u201cPerformance Improvements in .NET 9\u201d article.<\/p>\n

Closing<\/h2>\n

.NET 9 sees a large number of new features and quality of life improvements with a focus on JSON schema and intelligent application support. In total 46 pull requests<\/a> contributed to System.Text.Json during .NET 9 development. We\u2019d like you to try the new features and give us feedback on how it improves your applications, and any usability issues or bugs that you might encounter.<\/p>\n

Community contributions are always welcome. If you\u2019d like to contribute to System.Text.Json, check out our list of help wanted issues<\/a> on GitHub.<\/p>\n

The post What\u2019s new in System.Text.Json in .NET 9<\/a> appeared first on .NET Blog<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"

The 9.0 release of System.Text.Json includes many features, primarily with a focus on JSON schema and intelligent application support. It […]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[7],"tags":[],"class_list":["post-1333","post","type-post","status-publish","format-standard","hentry","category-dotnet"],"_links":{"self":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/1333","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/comments?post=1333"}],"version-history":[{"count":0,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/1333\/revisions"}],"wp:attachment":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/media?parent=1333"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/categories?post=1333"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/tags?post=1333"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}