I would like to request the data-query package support filtering on OData collections using lamdba functions. Given a Collection with the existing operators, the filter string outputted by `toODataString` should be OData v4 compliant.

Example: Project is a collection. A user filters to see all General projects which outputs { field: 'Project', operator: 'eq', value: 'General' }.

Recommendation: Supply another key that dictates the lamdba operator and property field to use.

{ field: 'Project', operator: 'eq', value: 'General', lambda: 'any', collectionField: 'Name' } -> $filter=Project/any(x:x/Name eq 'General')

The above can work with inner functions like contains.

{ { field: 'Project', operator: 'contains', value: 'gen', ignoreCase: true, lambda: 'any', collectionField: 'Name' } -> $filter=Project/any(x:contains(tolower(x/Name),'gen'))

Request:

- provide a boolean property "virtualScrolling" on component GridColumnMenuCheckboxFilter which allows rendering a large list of filter options without delay

Discussion:

- https://www.telerik.com/forums/gridcolumnmenucheckboxfilter-virtual-scrolling

Use case:

- there are a lot of options to filter already in memory

- the filter dropdown has to open quickly (it opens slowly now, because there are so many options)

- after opening, the user sees a huge list (i.e. a long scrollbar)

- so he starts making the list of options smaller using the search input

Here's a screenshot with 100 options. 

Alternatives:

From a developer point of view I think a scrollable filter is the most convenient way to handle the problem.

An alternative would be to provide a handler whenever the user selects a combobox in the GridColumnMenuCheckboxFilter. Then we could cut the number of options after a threshold and an option / combobox labelled "show more". When this is clicked, the filter options are re-rendered, the lists gets longer - and the user will get annoyed and will making the list of options smaller using the search input.

An other alternative would be to have a possiblity to force the user right away to use the search box. Instead of showing the list of checkboxes a text would be shown: "1258 options. Please refine your search input." But this would be a more invasive option.

Provide built-in scrolling of the Chart.

It should work similar to the pannable but allows scrolling with the mouse wheel instead of zooming.

The required end result is similar to this:

https://stackblitz.com/edit/react-rgpxmk-nrntv1?file=app/main.jsx

Add render function/prop for the ColorPicker popup.

This will allow rendering custom elements inside the ColorPicker Popup.

Allow sorting per column by a field other than the displayed field on the column. This goes for group sorting as well, when grouped by a certain field, the groups can only be sorted by that field, when we actually need those groups sorted in an arbitrary order we have defined in another field on the data.

https://github.com/telerik/kendo-react/issues/633

The Angular ButtonGroup has a 'selection' property that is not present in the React ButtonGroup. 

This functionality would be nice to have in React.

import React from 'react';
import ReactDOM from 'react-dom';

import { Button, ButtonGroup } from '@progress/kendo-react-buttons';

class ButtonGroupContainer extends React.Component {
  state = {
    selected: null
  }
  groupButtonClick = (e) => {
    this.setState({
      selected: e.target.id
    })
  }

  isSelected = (index) => {
    return index === parseInt(this.state.selected) ? true : false
  };

  render() {
    return (
      <div className="row">
        <div className="col-xs-12 col-sm-6 example-col">
          <ButtonGroup>
            <Button togglable={true} id={1} selected={this.isSelected(1)} onClick={this.groupButtonClick}>
              Bold
                     </Button>
            <Button togglable={true} id={2} selected={this.isSelected(2)} onClick={this.groupButtonClick}>
              Italic
                     </Button>
            <Button togglable={true} id={3} selected={this.isSelected(3)} onClick={this.groupButtonClick}>
              Underline
                     </Button>
          </ButtonGroup >
        </div>
      </div>
    )
  }
}
ReactDOM.render(
  <ButtonGroupContainer />,
  document.querySelector('my-app')
);

I'm looking at implementing a Chart with multiple ChartPane, each with their own legend displaying only the series displayed in the respective pane.

Here is an example of the layout with separate charts: https://stackblitz.com/edit/react-xtyhbu-muedhd?file=app%2Fmain.js 

After speaking with support, they suggested I created a feature request here.

Currently, this is possible with CSS animation only:

https://github.com/telerik/kendo-react/issues/326

The DatePicker component has a `toggleButton` prop which we use for customisation, but this prop is missing from DateTimePicker and TimePicker, this makes an inconsistent API and is frustrating for us because we cannot easily apply the same customisation to them.

Please can you add `toggleButton` prop to DateTimePicker and TimePicker.

Hi

We use the directory upload feature in our MVC app using Kendo. We are now redeveloping the app using React but this feature is missing. 

Is this feature on the roadmap for a future update (soon)?

Kind regards

Rakesh

The KendoReact MaskedTextBox value cannot be cleared once a value is set. See this forum post for examples and a proposed workaround: https://www.telerik.com/forums/maskedtextbox-cannot-be-cleared

I would like for a user to be able to clear the MaskedTextBox value without having to code it as a special case in the onChange event handler. I believe this should be done by default as per the Kendo jQuery MaskedTextBox, but it could also be optional via a prop or clear button.

Can the Kendo UI Multiselect possibly select the "active" item when tab is pressed? It currently does this for the enter key.

We are building a Typescript Create React App application, and we would really like to be able to allow our users to type a partial entry and then allow tab to complete the selection and move on to the next input.

I tried to make it have this behavior but it became a fairly large mess and seems like it could be facilitated in the source code with less mess.

Even possibly just exposing access to more events would make it easier, like an onKeyDown, but that would still require some additional code to figure out what the current active item is.

Currently using these below, not sure what "Version" below in this form those belong to so I just guessed:

WHAT:
Add custom cell rendering option for MultiColumnComboBoxColumn. Just like the 'cell' in GridColumnProps.

I am trying to create a radial gauge with gradient fill but I don't see any help regarding this. Please see the below image of what actually I am looking for. 

Is it possible to have a multirange support in the RangeSlider like the following (https://zillow.github.io/react-slider/):

It could be helpful to get multi range values using only one component. Easier for the developer to manage the data and for the user to select it.