Open akhenry opened 4 years ago
The use case for this is when tables is extended in places like session selector etc, we can just disable for telemetry tables, and enable via a prop
@akhenry - the event should not get emitted in the usual use case of TelemetryTable.js, and in the use cases we do have we can extend and emit that event, that way performance in tables will not be impacted
I have a fix for this in PR #3325
I still don't quite understand why it would be necessary to scan existing rows to see if they are marked. Marking is not persisted, so don't we just build it up dynamically as users mark and unmark rows?
We have use cases where we want to dynamically mark rows outside of the view (eg in session tables), to show users what sessions they are already connected to.
Currently the telemetry table view scans all table results as soon as they are returned to compile a list of marked rows. We need to find a better way of doing this, because doing it up front with large data sets adds to view load time. Could it happen on demand?