From bf09c87f87feb297efeb587ad01827550ba38143 Mon Sep 17 00:00:00 2001 From: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com> Date: Mon, 18 Sep 2023 13:48:11 +0200 Subject: [PATCH] Mention MultiUrlPickerValueConverter instead (#14818) Co-authored-by: Zeegaan --- .../DefaultPropertyValueConverterAttribute.cs | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/src/Umbraco.Core/PropertyEditors/DefaultPropertyValueConverterAttribute.cs b/src/Umbraco.Core/PropertyEditors/DefaultPropertyValueConverterAttribute.cs index b74d9903cf..a414d76542 100644 --- a/src/Umbraco.Core/PropertyEditors/DefaultPropertyValueConverterAttribute.cs +++ b/src/Umbraco.Core/PropertyEditors/DefaultPropertyValueConverterAttribute.cs @@ -16,11 +16,10 @@ public class DefaultPropertyValueConverterAttribute : Attribute /// a DefaultPropertyValueConverter can be more specific than another one. /// /// - /// An example where this is useful is that both the RelatedLiksEditorValueConverter and the JsonValueConverter + /// An example where this is useful is that both the MultiUrlPickerValueConverter and the JsonValueConverter /// will be returned as value converters for the Related Links Property editor, however the JsonValueConverter - /// is a very generic converter and the RelatedLiksEditorValueConverter is more specific than it, so the - /// RelatedLiksEditorValueConverter - /// can specify that it 'shadows' the JsonValueConverter. + /// is a very generic converter and the MultiUrlPickerValueConverter is more specific than it, so the + /// MultiUrlPickerValueConverter can specify that it 'shadows' the JsonValueConverter. /// public Type[] DefaultConvertersToShadow { get; } }