Dear kendo ui team.
You publish really helpful sample projects. Taking a closer look you use unofficial APIs to solve the problems. This means you don't support those solutions in typescript and tehre is no documentation for them to understand what else could be done with those APIs. That's really unfortunate.
One of those helpful examples is found here. kendo.timezone and kendo.date seem to be unofficial APIs, since they are not includede in the typescript definition.
<script>
function
getAdditionalData() {
var
scheduler = $(
"#scheduler"
).data(
"kendoScheduler"
);
var
timezone = scheduler.options.timezone;
var
startDate = kendo.timezone.convert(scheduler.view().startDate(), timezone,
"Etc/UTC"
);
var
endDate = kendo.timezone.convert(scheduler.view().endDate(), timezone,
"Etc/UTC"
);
//optionally add startTime / endTime of the view
var
startTime = kendo.date.getMilliseconds(scheduler.view().startTime());
var
endTime = kendo.date.getMilliseconds(scheduler.view().endTime());
endTime = endTime == 0 ? kendo.date.MS_PER_DAY : endTime;
var
result = {
Start:
new
Date(startDate.getTime() - (startDate.getTimezoneOffset() * kendo.date.MS_PER_MINUTE) + startTime),
End:
new
Date(endDate.getTime() - (endDate.getTimezoneOffset() * kendo.date.MS_PER_MINUTE) + endTime)
}
return
result;
}
</script>
Using those APIs in your official sample projects makes those APIs somehow official. Would be nice if you honor that in your documentation and typescript definitions.
Kind regards
Bernd