Hi Kendo Angular team,
It will be a nice improvement if there is an option to set a specific type for the Grid data item and the templates. This will allow checking the types inside the templates when fullTemplateTypeCheck is on.
Currently the pager is always at the bottom of the grid. I would love to see an option to place the pager at the top and/or bottom. Without adding custom code every time I need this.
i am using Telerik Angular Editing Grid for list editing of data.one of our main requirements is to copy a cell value and multiselect cells to paste data. this requires Angular grid to provide out of the box multi cell selection mode so that upon action respective cell values get updated
Essentially the most basic GridComponent when ngIf'd in and out will not be collected -- apparently because of orientation change / resize change listeners not being appropriately removed.
Steps to Reproduce
Click the TOGGLE TABLE button to hide the table
Click the TOGGLE TABLE button to show the table
repeat several times
Take a memory snapshot
There will be HTMLTableRowElement items that grow each iteration of toggling the table.
The HTMLTableRowElements retention shows that they eventually lead to a resize listener, or an orientation change listener.
Since the client side filtering honours ignoreCase and the toOdatastring not, we got a difference in behaviour, so i'd like to report this as a BUG! With dropdowns I use: &$filter=contains(tolower(FieldName), tolower('" + searchString + "')) but for grid filtering a COLUMN BASED ignoreCase is a MUST!
The filter descriptors support accessor functions in the "field" option. It would be great to see this implemented in the sort, group, and aggregate options. const result = process(items, { filter: { logic: "and", filters: [{ field: x => x.getValue(), operator: "eq", value: 0 }], // <- supported }, group: [ field: x => x.getValue(), // <- not supported aggregates: [{ aggregate: "sum", field: x => x.getValue() }] // <- not supported ], sort: [{ field: x => x.getValue(), dir: "desc" }] // <- not supported });
We would like to have the possibilty to create custom implementation of grid columns (or any other control/component). Because we also have this in our WPF projects and it was very useful to minimize the redundant code and also the "initialization code". This can't be done in a simple template, for example we need to inject services and get data etc.. Example: In our WPF project have lots of different grids with values related to units. The cell can convert this unit to and other unit itself, it can localize the texts, it shows the information in some kind of "progress bar", has a tooltip, etc... And all we have to do in the code is to set a column like this <custom-column valueField="test" unitField="test2" />. It would be great to have this feature in the Angular 2 grid as well.
Support TYPE in DataResult (speciallly GridDataResult) In state you would like to do something like: export interface SomethingState { loading: boolean; success: boolean; data: GridDataResult<XYZ> } it would be State with data: XYZ[].
Support for showing and hiding rows in angular grid
Currently, the fieldname is used as "clue" when dragging a column header from the grid. However, this name is rarely appropriate (for instance, it could the name of the correpsonding property in the DTO between back-end/front-end, or it could be a normalized English name while the user is browsing in French, etc.). We would prefer to have either a configurable text, or else use the text currently specified as "title" for the column.
Currently the filterCellTemplate is ignored for commnand column. It would be a handy feature if one could specify also content of filter cell for command column so in case filtering is enabled we could for example provide some suctom additional functionaly/content in that column (for example i wanted to add there a button that would reset all filters)
The group panel on the grid should be configurable to be hidden
Implement "Shift + Arrow Keys adds the row which holds the focused cell to the selection (only for selection mode "multiple")", explained here (https://demos.telerik.com/kendo-ui/grid/keyboard-navigation)
Please make the grid selection cancelable.
Just like KendoUI supports offline datasource sync.
It way too complicated to clear the selection programmatically in the grid at the moment. Please add a clearSelection method on the grid instance.
As described here: https://github.com/telerik/kendo-angular/issues/731 The function toODataString not generate the string with the groupby and aggregate. In order to the groupby funtionality of Grid component to work with OData, this is needed. Sample (code) available at https://github.com/telerik/kendo-angular/issues/731
In a Kendo grid, Angular/MVC/JS/Whatever; When using multi check filter. ---- Only show those values that are still useful to filter on!!! --- When filtering is done(one to many columns) - ONLY the remaining options should be seen when setting the NEXT filter (not all possible values in the database) of course distinct and sorted (the grid could have an option of doing it this way or the old way) example: let's say we have 5 numbers of categories, each category have 20 different details. when filtering is set on one category, then when filtering on details - only the 20 remaining details should be seen, not 100(5*20) and vice verse, if filtering one detail - only one category should be seen when filtering on category.
Kendo Angular PDF is currently has good functionality to export/download as PDF. My Idea is that , if Kendo can extend its PDF export functionality with print also. Problem - Currently using kendo PDF download, the GRID or any HTML component looks good to the users. But the same Grid if the user want to print , then the developers has to use some third party scripts to generate the print object and do the print. still its not appears as good as it appears in PDF. so the end users are complaining why the PDF export and the print is different in look and feel. Here are the steps to overcome. 1. should have a print PDF functionality which opens the PDF into new window. 2. the user has the option to download or print the pdf using PDF in-built options. 3. Kendo to provide fix to open in new window for all browsers ( IE, chrome, firefox etc) 4. Kendo print should not send the request to underline printer or any other hardware device.
Suggestion: Make the 'select all' checkbox in the grid more intuitive for the user. When we combine virtuall scrolling and selection via checkboxes for the kendo grid the 'select all' checkbox in the header will only select rows which are already visible / paged in. This is of course because kendo does not yet now about the not yet paged in rows. On the other side this behavior is quiet unintuive for the user. The user does not know about page border and expects the select all checkbox to check all rows. The desired functionality could be realized by internally differentiating between two selection modes, one where the selected rows are are accessible via api (normal mode) and one where the deselected rows are accessible via api (mode where select all is enabled). This would increase the user experience.