in 0.3.0 release I was able to describe a column by percentages. i.e. <Column field="certification" title="Certification" width="40%" /> This no longer works in the 1.0.1 release
As in the JQuery Version, the Column Menu with selection for filter and making columns viewable, is something that makes this table solution unique. https://demos.telerik.com/kendo-ui/grid/column-menu For the solution, putting the column Definition into the state object is an Option.
Currently the GridColumn Component only supports width property. It should also support minWidth and maxWidth properties for better responsive design. https://www.telerik.com/kendo-react-ui/components/grid/api/GridColumnProps/
As in the JQuery version, it would be good to have the option of showing the total of a column's values without having to use grouping aggregates. For example i have 10 products with their prices and i would like to see their total cost in a row below the column, without having to use grouping which adds more elements to the Grid.
In Panelbar , when we set expandmode set to 'single' it do not toggle the item . it only works with expandmode 'multiple'. We should also allow to toggle a panelbar item in 'single' mode a use case could be -i want to close all of the items in single mode
I'm looking to conditionally set the background color of a row, much like this example for jQuery: https://docs.telerik.com/kendo-ui/controls/data-management/grid/how-to/Layout/style-rows-cells-based-on-data-item-values
Currently there is no way to pass custom rendering component into header template (in jQuery version there was headerTemplate). For example, you are exposing headerSelection prop, but what if I want to render fancy Material UI checkbox there. Currently I do not have ability to do that with native react flow.
Please add a possibility to customize Kendo UI Grid for React pager text like "Page ... of ...." or "... of items" or to pass own strings.
Please, add a possibility to integrate inline edit in Kendo UI Grid for React (@progress/kendo-react-grid, 0.3.0) with ReduxForm (https://github.com/erikras/redux-form) and/or FinalForm (https://github.com/final-form/react-final-form) which will make easier work on validating data and more uniform code style for form validation (as packages mentioned above are the de facto standard in working with forms in React-Redux applications).
It would be great to have a TreeList component similar in appearance and behavior to the jQuery TreeList (https://demos.telerik.com/kendo-ui/treelist/index), but with the kind of support for virtual scrolling built into the native KendoReact Grid component.
A React wrapper exists for the jQuery TreeList, but it still doesn't play nicely with React, and in any case only supports paging for displaying large data sets, which is inherently not intuitive for displaying tree structures where parent / child hierarchies might span multiple pages.
My sense is this native component would basically be the Grid, but with support for hierarchical data, including drag-and-drop re-ordering of parent / child relationships.
Thanks for considering this feature.
Currently the GridFilterCell OnChange returns a subset of a FilterDescriptor (A value an an Operator to run on the value), which allows a custom filter cell to create one filter rule (FilterDescriptor). However, the CompositeFilterDescriptor structure allows a lot more flexibility. `month == 'January' OR 'March' OR 'May'`. If the GridFilterCell could be passed a CompositeFilterDescriptor instead of the current subset, then a custom filter cell could be much more powerful.
In an orders grid for instance, with a status of Pending, Paid, Shipped, and Delivered a "Show/Hide Shipped" button would exclude or include the Shipped and Delivered orders when clicked. Or a list of checkboxes to choose the statuses you want to see (like the JQuery Grids support).
TL;DR: There is currently no way to re-implement multi-checkboxes or other complex filtering interfaces with the Kendo React Grid without re-implementing all of the filtering logic manually from scratch, as the Existing filter cells don't support this and a custom GridFilterCell can't be configured to return that logic in a single FilterDescriptor.