leekelleher 5295c6fc6d Property Editor: Number - set numeric value ...

This was setting the value as a `string`, which would cause issues
when used in certain scenarios, e.g. MNTP min/max configuration,
the value would assumed to be numeric, but it'd be a string, so
conditions like `max === 1` would be false, as it'd be `"1"` instead.

Ensuring the value is a `number` before the "property-value-change"
event is sent appears to resolve this issue.

2024-01-08 10:24:16 +01:00

src/Umbraco.Web.UI.Client

Property Editor: Number - set numeric value

2024-01-08 10:24:16 +01:00

Description

Umbraco is a free and open source .NET content management system helping you deliver delightful digital experiences.

448 MiB

Languages

C# 59.5%

TypeScript 39.9%

JavaScript 0.3%

HTML 0.2%