Hi Team,

Can you consider the implementation of a Native TileLayout component? 

It will be a very nice add-on to the Native Vue suite.

For Vue components, the v-model on a multi-combo box and every component must bind to the underlying object.
:value-primitive="false" doesn't work as per some suggestions.

v-model binding to the underlying object is a MUST HAVE, Top priority, number one with a bullet. Without it, your components are a PITA to use and my current proof of concept might end here and we won't use your components with some bigger projects coming down the line.

Currently, the Kendo UI for Vue suite has only a Scheduler Wrapper component.

It would be nice if we can see a native version of the component.

Can you please provide a native Vue Wizard Control like the JQuery one:

Demo of core features in jQuery Wizard widget | Kendo UI for jQuery (telerik.com)

Hello Team

Selection/Highlight of the Main Menu is incorrect, when the child item of different submenu is chosen. This is UI/UX glitch and would helpful if resolved

Code Snippet : https://stackblitz.com/edit/nrqsrn?file=src%2Fmain.js

Do you have a development plan?

Steps to reproduce:

(latest version of vue, vue CLI, node etc. installed globally)

• vue create test-project
• cd test-project
• npm install --save @progress/kendo-ui
• npm install --save @progress/kendo-theme-default
• npm install --save @progress/kendo-dateinputs-vue-wrapper
• added Calendar component to App.vue (see https://www.telerik.com/kendo-vue-ui/getting-started/)
• changed the name "kendo-calendar" in HTML template to "Calendar", otherwise I get build errors
• npm run serve --> browse to localhost:8080 --> error in console:

Uncaught ReferenceError: $ is not defined
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:85)
    at Object.eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:292)
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:74)
    at Object.1472 (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:75)
    at __webpack_require__ (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:21)
    at Object.0 (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:49)
    at __webpack_require__ (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:21)
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:41)
    at eval (webpack-internal:///./node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js:44)
    at Object../node_modules/@progress/kendo-ui/js/pdf-viewer/pager.js (app.js:3624)

I could reproduce the error using different Kendo UI for vue components like Buttons etc. (following the getting-started page for the button component). The default vue project template uses Babel and Webpack. Is there a configuration missing for Kendo UI?

I already checked:

• https://www.telerik.com/kendo-vue-ui/getting-started/
• https://www.telerik.com/support/whats-new/kendo-ui?utm_medium=internal&utm_source=yellowribbon&utm_campaign=kendo-ui-vue-awareness-r22019release#vue-updates-in-r2-2019
• https://www.telerik.com/blogs/what-you-need-to-know-about-vue-cli-3
• https://www.telerik.com/blogs/better-tooling-with-the-new-vue-cli
• https://www.telerik.com/blogs/integrating-vue-cli-3-with-kendo-ui
• https://www.telerik.com/blogs/creating-and-managing-vue-projects-with-vue-ui

Hi. 

I am looking for a Badge component in the Kendo UI for Vue suite. The component is available for the Angular suite(https://www.telerik.com/kendo-angular-ui/components/indicators/badge/) but not for Vue.

It will be nice to have this component available also for Vue.

The following packages should be added as peer dependencies to the @progress/kendo-vue-data-tools package:

• "@progress/kendo-svg-icons"
• "@progress/kendo-vue-popup"
• "@progress/kendo-vue-animation"

Describe the bug
The @progress/kendo-licensing is missing as peer to data-tools package

The DatePicker, DateTimePicker, TimePicker, and DateRangePicker components don't provide open and close events that are triggered when the popup of a component is opened/closed. 

Describe the bug
When using a slot to define the columns in the Wrapper Grid, the result in Vue 2 and Vue 3 is different.

• In Vue 2, if we pass 2 columns to the slot, only these two columns are rendered in the component.
• In Vue 3, no matter how many columns we pass to the slot, the component renders all columns, based on the data in the datasource

To Reproduce
Check the two examples below:

• Vue 2 - https://codesandbox.io/s/jovial-hamilton-k6hfl7?file=/src/App.vue
• Vue 3 - https://codesandbox.io/s/empty-smoke-cnyz0t?file=/src/App.vue

The two examples use the same implementation but the number of columns rendered in each Grid is different

Expected behavior
The two examples should work the same way as in the Vue 2 application.

Screenshots
Vue 2:

Vue 3:

Describe the bug

<multiselect
        :data-items="values"
        :value="values"
      ></multiselect>
...
data() {
    return {
      values: [2,3],
    };

select and item
error:

At TagList.js:81
Uncaught (in promise) TypeError: tagData.text.replace is not a function
at Proxy.eval (TagList.js:81:48)
at Array.map ()
at Proxy.render (TagList.js:75:19)
at renderComponentRoot (runtime-core.esm-bundler.js:623:44)
at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js:4372:57)
at ReactiveEffect.run (reactivity.esm-bundler.js:195:29)
at setupRenderEffect (runtime-core.esm-bundler.js:4498:9)
at mountComponent (runtime-core.esm-bundler.js:4281:9)
at processComponent (runtime-core.esm-bundler.js:4239:17)
at patch (runtime-core.esm-bundler.js:3843:21)

Hi,

I'm trying to figure out how to persist and restore state in the native Vue grid.  Am I missing something; is this not available yet?

I found the article about doing it with the grid wrappers, but not native.

Thanks!

The PanelBar component is currently available only as a Wrapper component.

To use all the benefits provided by the Vue ecosystem, it will be very convenient if the component is available as a Native one. 

I'm submitting a Bug report

Current behavior

<chart :title-text="'Gross domestic product growth /GDP annual %/'" 
        :legend-position="'bottom'"
        :series-defaults-type="'area'"
        :category-axis-categories="categoryAxisData"
        :category-axis-major-grid-lines-visible="false"
        :category-axis-labels-rotation="'auto'"
        :value-axis-labels-format="'{0}%'"
        :value-axis-line-visible="false"
        :value-axis-axis-crossing-value="-10"
        :tooltip-visible="true"
        :tooltip-format="'{0}%'"
        :tooltip-template="tooltipTemplate"
        :theme="'sass'">
    <chart-series-item :name="'India'"
                        :data="indiaData"
                        :line-style="'smooth'">
    </chart-series-item>
    <chart-series-item :name="'World'"
                        :data="worldData"
                        :line-style="'smooth'">
    </chart-series-item>
    <chart-series-item :name="'Haiti'"
                        :data="haitiData"
                        :line-style="'smooth'">
    </chart-series-item>
</chart>

When using the ChartSeriesItem tags to define the data in the Chart component the following error appears in the console once the Vue project is started.

Expected behavior

<chart-series-item :name="'India'"
                        :data="indiaData"
                        :line-style="'smooth'">
    </chart-series-item>
    <chart-series-item :name="'World'"
                        :data="worldData"
                        :line-style="'smooth'">
    </chart-series-item>
    <chart-series-item :name="'Haiti'"
                        :data="haitiData"
                        :line-style="'smooth'">
    </chart-series-item>

Using a definition like the above, we should be able to define Chart's data with no issues.

Minimal reproduction of the problem with instructions

1. Open this project
2. In the console run "npm install"
3. In the console run "npm run serve"
4. Open the URL of the project and see the browser's console