From 4a0187678e46c638a161d0fcc1340016f53a4406 Mon Sep 17 00:00:00 2001 From: Mike Alhayek Date: Mon, 25 Mar 2024 12:11:11 -0700 Subject: [PATCH] Update 1.9.0 Release notes after STJ recent changes (#15587) --- src/docs/releases/1.9.0.md | 18 ------------------ 1 file changed, 18 deletions(-) diff --git a/src/docs/releases/1.9.0.md b/src/docs/releases/1.9.0.md index 38a9c99cc86..436c638e1e3 100644 --- a/src/docs/releases/1.9.0.md +++ b/src/docs/releases/1.9.0.md @@ -8,24 +8,6 @@ Release date: Not yet released The utilization of [Newtonsoft.Json](https://www.nuget.org/packages/Newtonsoft.Json) has been discontinued in both **YesSql** and **OrchardCore**. Instead, we have transitioned to utilize `System.Text.Json` due to its enhanced performance capabilities. To ensure compatibility with `System.Text.Json` during the serialization or deserialization of objects, the following steps need to be undertaken: - - If your custom `Document` includes a collection with a getter-only property, it is imperative to incorporate a setter or utilize the `init` modifier to facilitate the assignment of values by `System.Text.Json`. For instance: - -```csharp -public class MediaProfilesDocument : Document -{ - public Dictionary MediaProfiles { get; } = new(StringComparer.OrdinalIgnoreCase); -} -``` - -Should be changed to the following instead: - -```csharp -public class MediaProfilesDocument : Document -{ - public Dictionary MediaProfiles { get; init; } = new(StringComparer.OrdinalIgnoreCase); -} -``` - - If you are using a custom deployment steps, change how you register it by using the new `AddDeployment<>` extension. This extension adds a new service that is required for proper serialization. For instance, instead of registering your deployment step like this: ```csharp