aspnetcore: Cannot bind to nullable types (bool?, int?, etc)

@SteveSandersonMS

What would it mean though? How would the UI state ever be “null”?

The UI state is “empty” - the initial state. For example when you bind an <input type="number"> to int? which is currently null the input should stay empty.

I believe both React and Angular behave in a similar way.

In my opinion it is a must have feature. Hopefully @SteveSandersonMS will agree.

So, will we allow nullables? If so i’ll see if I can implement the others as well in #1012

1. int?
2. long?
3. bool?
4. float?
5. double?
6. decimal?

Thanks for contacting us. We think that this issue is fixed now. If you are still facing this problem, please file a new issue.

Supporting DateTime? is also needed for <input type="date"> and <input type="datetime-local">

A nullable bool should show nothing, but it is usefull when you want to bind the value, like we’re doing here If the checkbox is interacted with, it should be true or false but initially it should be nothing.

<p>
    Initially null checkbox:
    <input id="checkbox-initially-null" bind="checkboxInitialltyNullValue" type="checkbox" />
    <span id="checkbox-initially-null-value">@checkboxInitialltyNullValue</span>
</p>

@functions{
    bool? checkboxInitialltyNullValue = null;
}