1. Feedback
  2. Blazor
  3. 27858

Welcome to the Blazor feedback portal. We’re happy you’re here! If you have feedback on how to improve the Blazor, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

In-Place Editor fails to properly handle nullable DateTimes

The In-Place Editor does not properly handle Nullable DateTime objects.  If the bound variable is null the component will throw an exception that looks like this:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Syncfusion.Blazor.InPlaceEditor.SfInPlaceEditor`1.d__318[[System.Nullable`1[[System.DateTime, System.Private.CoreLib, Version=5.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], System.Private.CoreLib, Version=5.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
   at Syncfusion.Blazor.InPlaceEditor.SfInPlaceEditor`1.d__63[[System.Nullable`1[[System.DateTime, System.Private.CoreLib, Version=5.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], System.Private.CoreLib, Version=5.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
   at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)

To easily reproduce the issue you can go to the Blazor demo and try to clear out the value in the first In-Place Editor Control with a label of "

DatePicker
".  When you try to submit the value change exceptions are thrown.

Because the demo uses Nullable DateTime Types I would assume the component is meant to support them.

https://blazor.syncfusion.com/demos/in-place-editor/date-pickers?theme=bootstrap4