Loving the new table however I ran into a strange behaviour that I'm not sure is intentional or not, either way, it leads to some weird behaviour.
I added a "Row click" event handler to my table, the action for that handler is to open another app. Our team prefers being able to click anywhere on the row to trigger something so we've opted to not use an action on the row. The weirdness comes when you click on a column header for sorting, when you do that the "Row click" handler is triggered which is weird because I wouldn't consider the column header to be a row, but I guess that's how it's modelled internally?
Either way, I tried to disable my action if the
selectedDataIndex == 0 but unfortunately the column header row and the first row share an index of
0, which is also strange?
Does anyone know how to have a row click handler but not have it be triggered when a column header is clicked? I'd like to support sorting and if the row click handler fires whenever click on a column that makes it's impossible.