Last Updated: 03 Jan 2022 12:17 by Benoit
Created on: 14 Dec 2021 07:46
Category: UI for Blazor
Type: Feature Request
Provide support for DateOnly and TimeOnly structs for the respective pickers

I would like to use the new structs that are part of .NET6 - the DateOnly and TimeOnly. 

Their support should extend to all respective date and time pickers and more complex components like the Grid, Gantt, Scheduler, and other applicable components. 

Posted on: 03 Jan 2022 12:17

We have evaluated the solution of custom modifications, but on this issue as on other know issues too (Scheduler customization, EditorTemplate validation...) this involve rather deep modification and the time to develop/merge them don't seems profitable.

On this particular issue, we will deal with the easy part (the pickers) by using other components, and for the hard part (components using the pickers) some are already deem to be replaced. Some are left, but if we have valid replacements before the fixes we may remove Telerik from our project.

That's not the outcome I expected when I started to use the Blazor component as I found them easy to use and very stable, but unfortunately they fall a bit short when we want to tailor our UI. I hope the coming updates will make us change our mind!

Posted on: 21 Dec 2021 13:25

Hello Benoit,

I agree that the new DateOnly and TimeOnly structs will be beneficial for both developers and us. We will certainly support them in the future.

It is evident that this novelty is important for your business. If it is also urgent, you may want to consider using a custom build of our source code, now that we provide it.

Our research showed that there is a need for multi-targeting to adopt Date/TimeOnly, which we prefer to avoid. That's why, we will wait to see what is the demand for the new structs and reconsider. In the worst case scenario, we will add support for Date/TimeOnly in late 2022 when we drop support for .NET 3.1 and 5.

On a side note, I understand that we may have different perception about what should represent .NET 6 compatibility. Application code that uses our APIs will compile, and our components and all functionality will work in .NET 6 projects. We do not claim integration with all .NET 6 features.

We will update this thread when we have additional information to share.

Progress Telerik

Learn about the important changes coming in UI for Blazor 3.0 in January 2022!
Posted on: 14 Dec 2021 15:21



I can understand that changes to support new versions of .Net can be delayed because you have urgent issue to fix first, but if you don't plan to support those new BCL types at all can you remove your "Compatibility with .Net6" from your website? Because that's what BCL types are, the base of .Net. It's not a functionality, it's truly compatibility.

One of the most interesting point of Blazor is to reuse classes from the C# backend, if we have to map them to a telerik-compatible model every time, we loose all the gain. That the main problem we have with NodaTime today, most of the ecosystem - including .Net - don't understand it and we have to convert it everywhere. .Net 6 offer us a way out of this stalemate and we are going to take it.


Do we really have to consider Telerik as a roadblock to deal with?