Provide support for DateOnly and TimeOnly structs for the respective pickers

Progress® Telerik® UI for Blazor Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Completed

Last Updated: 24 Sep 2024 12:18 by ADMIN

Release 5.0.0 (15 Nov 2023) (R1 PI1)

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.

18 comments

ADMIN

Dimo

Posted on: 24 Sep 2024 12:18

@Andrew and whoever is interested - Min and Max parameters are ignored if the Value is DateOnly or TimeOnly

Regards,
Dimo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Andrew

Posted on: 20 Sep 2024 21:24

This says "Completed", but I am not able to use Min/Max on a DateOnly bound DatePicker:

minFollowUpDate is a DateTime because Min= requires that type. But FollowUpDate is a DateOnly field. In this example, Min= has NO effect and does not prevent me from selecting a Date prior to minFollowUpDate.

Only when I change FollowUpDate from a DateOnly to a DateTime does the Min validation start working.

So, was this feature request only "Half-Completed"? Thanks for any insight you have into this :)

Chris

Posted on: 03 Aug 2023 13:33

@Dimo - that's for the grid. I'm more interested in the date/time pickers supporting it.

ADMIN

Dimo

Posted on: 03 Aug 2023 13:25

@Chris - https://www.telerik.com/forums/filter-and-and-edit-datetimeoffset-grid-columns

Chris

Posted on: 03 Aug 2023 13:21

What about DateTimeOffset? When it that going to be supported???

It's amazing that this is not already supported.

ADMIN

Dimo

Posted on: 03 Aug 2023 13:04

@Benoit - our project always targets the lowest .NET version that we officially support, so this time it will be .NET 6. For the time being, we refrain from multi-targeting.

@Nuno - the Telerik.DataSource package is used by several products, so indeed, it's the main prerequisite for DateOnly/TimeOnly support for them too. I can't comment on the plans or readiness of other teams, so I recommend following the respective feature requests (I see ones for UI for ASP.NET Core and UI for .NET MAUI).

Benoit

Posted on: 03 Aug 2023 09:50

Hi Dimo,

Thanks for the update and provisory timeframe, it's appreciated.

I'd suggest you to go for 8.0 and not 6.0 in your migration through, as 6.0 end of life is also in 2024. Ending a migration so late that your target is already out of support looks as a joke, but not funny one for your users. And that's were we are with Telerik.

Nuno

Posted on: 03 Aug 2023 09:47

I'm a long-time client/user of Telerik suits of controls and tools, and I have to say that you guys used to be better at handling this kind of stuff. It seems that when you were "just" Telerik you were better than after being "Progress Telerik"

Should I dare to ask what about the other suites (kendo, Xamarin/Maui) will they be updated at the same time (I tried using the types some time ago and weren't available there also)?

ADMIN

Dimo

Posted on: 03 Aug 2023 09:40

Hello everyone,

The support for DateOnly/TimeOnly depends on a bigger task, which includes infrastructure changes in the source code of the whole Telerik UI for Blazor product (migration to .NET 6) and also the Telerik.DataSource dependency (related to data operations with the new types).

Our current plan is to implement all these changes + the DateOnly/TimeOnly support for early 2024 when we release the next major product version 5.0. I am sure this is not the timeline that you expected and I am sorry if this will require workarounds or refactoring in your apps. We also imagined we would deliver the feature earlier, but then we had to postpone it due to other high priority tasks.

Regards,
Dimo
Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Telerik family, check out our getting started resources!

n/a

Posted on: 03 Aug 2023 09:18

We also need support for Dateonly and TimeOnly

Rick

Posted on: 22 May 2023 20:44

We also have need of the DateOnly and TimeOnly structs.

Chris

Posted on: 22 May 2023 01:36

We bought 17 DevCraft licenses so far specifically for our teams to use the Blazor controls. Every freaking day it's something else that is half done. I was about to buy 10 more licenses with more on the horizon. We have 16 teams. This kind of stuff is ridiculous and I'm going to start looking elsewhere to transition to.

.NET 8 is almost here and you can't support a type that came out in .NET 6? Not even for a datepicker and timepicker???

I've noticed that every time something that should be included automatically in your controls is not, that there's a big song and dance about why it's actually better to not have the feature you need and then you all just create feature requests for it so it will die a quiet death. When Progress bought Telerik did they let most of the developers go or something? Why is version 4.2 of the Blazor controls still so lacking?

Nuno

Posted on: 11 May 2023 12:06

This is... for lack of better words, ridiculous. We're approaching .NET 8 GA and if one wants to use kendo with DateOnly or TimeOnly, we can't.

People it's 2023...wake up and smell the coffee, please..

ADMIN

Dimo

Posted on: 25 Jan 2023 07:55

Hi Dorian,

Our source code still support .NET 3.1 and we will drop that in some of the next releases. Then we will turn towards features such as this one.

Regards,
Dimo
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Dorian

Posted on: 25 Jan 2023 00:31

" 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."

What happened to this?

Benoit

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!

ADMIN

Dimo

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.

Regards,
Dimo
Progress Telerik

Learn about the important changes coming in UI for Blazor 3.0 in January 2022!

Benoit

Posted on: 14 Dec 2021 15:21

Hi,

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?