Last Updated: 13 Mar 2024 15:14 by ADMIN
Created on: 11 Jul 2022 13:35
Category: TimePicker
Type: Bug Report
timepicker value too restrictive - does not allow null/undefined

Currently angular will fail builds due to type check if kendo-timepicker value is null/undefined.

It requires it to always be a date - making it impossible to have initially empty values or to even reset the selection/value and show a placeholder.

Even the documentation for placeholder says:

Specifies the hint the TimePicker displays when its value is `null`.

private _value: Date = null;

@Input() public set value(value: Date)

But the input does not allow this. Even the property is defined in a way that would fail type checks in any newer angular project (strict mode is the default).

The only workaround currently is to  disable type check with $any()

Posted on: 13 Mar 2024 15:14

Hi Everyone,

I am happy to say that from version 15.2.0 our DateInputs accept null as a value.

Progress Telerik

Stay tuned by visiting our public roadmap and feedback portal pages! Or perhaps, if you are new to our Kendo family, check out our getting started resources
Posted on: 14 Oct 2022 12:18
Ahh, thank you so much!
Posted on: 14 Oct 2022 11:37

The workaround is to wrap the data binding with $any() until the improvement.


Posted on: 12 Oct 2022 19:18
Could you please expand on your workaround? I'm facing the same problem, and I'm not sure how you got around it.
Posted on: 18 Jul 2022 07:21

Hi Mauro,

Thank you for the provided feedback.

Indeed this is a known issue in our Date Inputs package and it is logged internally for enhancement of the package. I will update the status of the bug report to unplanned and when there is progress on the issue the status will also be updated.

We apologize for the inconvenience caused until the issue is resolved.

Progress Telerik

The Premier Dev Conference is back! 

Coming to you live from Progress360 in-person or on your own time, DevReach for all. Register Today.