Hello Syncfusion Team,
I’d like to request native support for the .NET TimeOnly type in the Syncfusion ASP.NET Core TimePicker and related controls.
Background:
With the introduction of the TimeOnly type in .NET 6, developers can now represent time-of-day values without a date component. This is a much cleaner solution for use cases such as scheduling, events, and scenarios where only the time is relevant.
Current Behavior:
Currently, the Syncfusion TimePicker component for ASP.NET Core only supports binding to DateTime, string, or sometimes TimeSpan. Attempting to bind directly to a TimeOnly property does not work correctly, and developers must create workaround properties and manually convert between types. This adds boilerplate code and potential for errors.
Requested Feature:
-
Allow the TimePicker (and any relevant controls) to bind directly to properties of type TimeOnly in ASP.NET Core Razor Pages.
-
Support TimeOnly both for initial value rendering and when posting back to the server.
-
Ensure two-way binding works seamlessly, similar to existing support for DateTime.
Benefits:
-
Aligns Syncfusion controls with modern .NET types and best practices.
-
Reduces the need for workarounds and extra code in the model/view.
-
Makes it easier for developers to build future-proof applications targeting .NET 6 and newer.
