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
We are currently passing some props down from Table to TableRow, or from both of them to TableCell, via context.
Those props are then used to dynamically set CSS classes in the children components. This means, every time those change, all components down the Table tree will need to re-render.
However, we could achieve something similar via CSS directly, reducing re-renders when not strictly needed.
We should be aware of the hazard of doing something in JS which can be done in pure CSS, but I think we can defer this until we find it actually causes us a problem - either for code maintenance or performance reasons.
We are currently passing some props down from
Table
toTableRow
, or from both of them toTableCell
, via context.Those props are then used to dynamically set CSS classes in the children components. This means, every time those change, all components down the
Table
tree will need to re-render.However, we could achieve something similar via CSS directly, reducing re-renders when not strictly needed.
The text was updated successfully, but these errors were encountered: