[RFC] Create table v2 to resolve performance issues #207
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #199
Status: requesting comments/feedback
This PR introduces table v2. Table v2 makes the following changes in an attempt to improve the lifecycle performance of the original table component:
I've only tested the performance difference in storybook dev build, but there's about a 40% improvement (1.29s -> .91s) in time to render a basic table with 4 rows. If we agree this is a reasonable approach, I'll stress test this approach using the bus schedule table (with lots of data). Assuming that goes well, I'll build out the remaining styles/features for this element and replace v1 table with this implementation.
Chrome Performance Profiles: