Umbraco.Slider default value validation error on publish (unless value is selected)

[stayawakesteve]

Which Umbraco version are you using?

17.0.1

Bug summary

When using an Umbraco.Slider data type, trying to save & publish a node results in a validation error unless a value is set.

Specifics

The validation error states "The value [initial value],0 is not expected to contain a range".

If you change the value (even if that's back to the initial value), then the validation passes and the node can be published.

This becomes a problem if the slider is being used on a tab/group that is usually left as default.

Here is a screenshot of the slider configuration I'm using (with "Enable Range" deselected)...

Steps to reproduce

• Create a new Slider data type using the following settings:
  • Minimum value: 0
  • Maximum value: 1
  • Enable range: off
  • Initial value: 0.5
  • Initial value 2: 0 (or leave blank)
  • Step increments: 0.1
• Create a doc type containing a property that uses that data type
• Create a new node/page with that doc type
• Click "Save & Publish"

NOTE: I have tried using integer values and the same issue presents itself

Expected result / actual result

No validation errors on the property if left to the default (initial) value

[github-actions]

Hi there @stayawakesteve!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[AndyButland]

I think this is the same issue as reported in #20771 and fixed via #20772 for 17.1. As such I'll close this as a duplicate.

Of course if you still find problems once you have tried the 17.1 release candidate, please feel free to re-open.