RadzenNumeric value issue with nullable values

Radzen.Blazor Components
1

If a RadzenNumeric is bound to a nullable property, nullability is not honored as expected.

Example Blazor:

<RadzenNumeric Name="thermometer" @bind-Value="thermometer.Temperature" 
           class="w-100" 
           @chan></RadzenNumeric>
<RadzenRequiredValidator AllowNull="false" Component="thermometer" Text="@StringResources.Word_Required"/>
<RadzenNumericRangeValidator Min="1" Max="500" AllowNull="false" Component="thermometer" Text="@StringResources.Phrase_OutOfRange"/>

If the “Temperature” value here, which is a nullable int (int?), is ever set to a number, the Radzen control will never allow it to be set to anything but a valid number. Or at least that appears to be the case.

So, if you set it to 0 on init, it will always be 0, even if the field is cleared.

The expected behavior for a null value is, once the field has been cleared and lost focus, the backing property should be set to null. Otherwise, the validators silently “succeed” because of the original initialized value.

2

No, that\s not true:

<div class="rz-p-12 rz-text-align-center">
    <RadzenNumeric @bind-Value=@value  />
    <RadzenButton Text="Clear" Click=@(args => value = null) />
</div>

@code{
    int? value;
}