From ea3712fb9633958b258df01d10ae4ca90d0165d3 Mon Sep 17 00:00:00 2001
From: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com>
Date: Tue, 25 Jul 2023 11:56:46 +0200
Subject: [PATCH] Remove v10 fix, as it hopefully should not be relevant for 14

---
 .../PropertyEditors/SliderConfigurationEditor.cs  | 15 ---------------
 1 file changed, 15 deletions(-)

diff --git a/src/Umbraco.Core/PropertyEditors/SliderConfigurationEditor.cs b/src/Umbraco.Core/PropertyEditors/SliderConfigurationEditor.cs
index fbf45a9c41..915e92d709 100644
--- a/src/Umbraco.Core/PropertyEditors/SliderConfigurationEditor.cs
+++ b/src/Umbraco.Core/PropertyEditors/SliderConfigurationEditor.cs
@@ -25,19 +25,4 @@ public class SliderConfigurationEditor : ConfigurationEditor<SliderConfiguration
         ioHelper, editorConfigurationParser)
     {
     }
-
-    public override Dictionary<string, object> ToConfigurationEditor(SliderConfiguration? configuration)
-    {
-        // negative step increments can be configured in the back-office. they will cause the slider to
-        // crash the entire back-office. as we can't configure min and max values for the number prevalue
-        // editor, we have to this instead to limit the damage.
-        // logically, the step increments should be inverted instead of hardcoding them to 1, but the
-        // latter might point people in the direction of their misconfiguration.
-        if (configuration?.StepIncrements <= 0)
-        {
-            configuration.StepIncrements = 1;
-        }
-
-        return base.ToConfigurationEditor(configuration);
-    }
 }