Closed fawda123 closed 1 year ago
Thanks for the bug report, it should be fixed in the v0.3.0.9000 development version (https://github.com/glin/reactable/commit/a396ccb6503ad3f30b4ea78933fe6325862d3518) now:
The problem was that aggregated rows were being given their own row indices like 0
and 1
, which doesn't make sense because they're not actual rows in the data. This was an oversight with the react-table v7 migration, and unfortunately doesn't have a good workaround besides staying on 0.2.3 or installing the development version.
Much appreciated @glin, thanks for all your work on this great package!
With the latest update to v0.3.0, using the
groupBy
argument with a custom cell color function creates incorrect colors for the grouped headers. It looks like the color from the previous row is used.With the previous version 0.2.3, the grouped headers had no color.