Closed MargaritaKartaviciute closed 1 year ago
Thanks for reporting this, Margarita. I'll look into this and get back to you.
@NancyMcCallB Any progress on this issue?
I apologize! I thought I had responded to you back in September.
The current implementation of the Table component tracks only the current row indices. Because the component is built on the react-data-grid, which is not well-maintained, we've decided to deprecate it in the next release and develop a replacement in our general-purpose React component library iTwinUI-react. To future-proof your code, it would be a good idea to look at that Table component rather than writing a custom data provider for this Table component. We'll be replacing our uses of Table internally with the iTwinUi implementation, as well.
The Table
component have now been completely removed due to lack of support of the underlying components. The @itwin/itwinui-react
package now offer a completely new table component which should be used instead this.
Closing this issue. Thanks.
Describe the bug
When rows selected in table and table sorted by column, previously selected elements don't change their location. After table sorting it seems that completely different elements was selected.
To Reproduce Steps to reproduce the behavior:
sortable
set to true:columns.push({ key: "current_class", label: "Original class", sortable: true }); columns.push({ key: "max_class", label: "Predicted class", sortable: true });
const dataProvider = new SimpleTableDataProvider(columns);
<Table dataProvider={_getDataProvider()} />