You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we do have a full state of the table. Toggling a table entry forces the full table to be re-drawn. This should be more efficient and only toggled rows should be re-rendered.
The text was updated successfully, but these errors were encountered:
Yes, the current implementation is actually using them. However, that still means that the whole table needs to be re-processes.
I would hope that there's a solution where each row becomes a component, and manages its own state. The downside of that might be that there is no (table) global state for expansions. Which might be ok in most scenarios I guess.
Then again, I guess we need to split up the current table component into smaller bits, and follow the idea of "composition" to build different ways of dealing with tables. Maybe having different approaches for different use cases.
#128 addresses the composition issue. So implementing this should be possible now. However, Table doesn't currently use state internally per row so that would still need to be implemented.
Currently we do have a full state of the table. Toggling a table entry forces the full table to be re-drawn. This should be more efficient and only toggled rows should be re-rendered.
The text was updated successfully, but these errors were encountered: