Document the removal of PopulateSettings in 1.9 release notes

src/docs/releases/1.9.0.md

@@ -44,6 +44,29 @@ services.AddJsonDerivedTypeInfo<UrlCondition, Condition>();
 
 In particular, any type introduced in custom modules inheriting from `MenuItem`, `AdminNode`, `Condition`, `ConditionOperator`, `Query`, `SitemapType` will have to use this method.
 
+ - The extension `PopulateSettings<T>(model)` was removed from `PartFieldDefinition`. If you are using this method in your code, you'll have to get the settings using the `Settings` object directly. For instance, if you have this code,
+
+ ```csharp
+ public override IDisplayResult Edit(ContentPartFieldDefinition partFieldDefinition)
+ {
+ return Initialize<NumericFieldSettings>("NumericFieldSettings_Edit", model => partFieldDefinition.PopulateSettings(model));
+ }
+ ```
+
+ You'll change it to the following:
+
+ ```csharp
+ public override IDisplayResult Edit(ContentPartFieldDefinition partFieldDefinition)
+ {
+ return Initialize<NumericFieldSettings>("NumericFieldSettings_Edit", model => 
+ {
+ var settings = partFieldDefinition.Settings.ToObject<NumericFieldSettings>();
+ model.Hint = settings.Hint;
+ // ...
+ });
+ }
+ ```
+
 ### Media Indexing
 
 Previously, `.pdf` files were automatically indexed in the search providers (Elasticsearch, Lucene or Azure AI Search). Now, if you want to continue to index `.PDF` file you'll need to enable the `OrchardCore.Media.Indexing.Pdf` feature.