Please make APIs used in your sample projects official/public.

2 posts, 0 answers
  1. Bernd
    Bernd avatar
    83 posts
    Member since:
    Feb 2013

    Posted 11 Sep 2016 Link to this post

    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 seem to be unofficial APIs, since they are not includede in the typescript definition.

        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 =;
            var endTime =;
            endTime = endTime == 0 ? : endTime;
            var result = {
                Start: new Date(startDate.getTime() - (startDate.getTimezoneOffset() * + startTime),
                End: new Date(endDate.getTime() - (endDate.getTimezoneOffset() * + endTime)
            return result;

    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



  2. Stamo Gochev
    Stamo Gochev avatar
    186 posts

    Posted 14 Sep 2016 Link to this post

    Hi Bernd,

    Thanks for your feedback.

    There are some APIs that are shared by several widgets and thus they are exposed in a handy way for internal usage. As some of them are not intended to be used outside of the Kendo UI (or depend on other internal functionality), they cannot be made official.

    However, this does not mean that they cannot be used when developing custom solutions (because complex scenarios usually require a lot of customizations). In addition, we are open for suggestions on exposing an API that you think is useful and can be applied in a variety of situations.

    You can post your ideas in our User Voice:

    Stamo Gochev
    Telerik by Progress
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top