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
I have an material table setup where one of the columns has a counter component to update the state of the table, this triggers a debounced update to the table data state, when profiling I noticed that there are two commits for the state change, one where only the data props change for the material table and another where the internal state for data, columns, orderByCollection, originalData, renderData, action changes. Can someone help me resolve to avoid re-mounting everything when the data changes on the component, what other areas can I look into, so far I have reduced the number of columns I am displaying to isolate the issue and also made sure I was passing stable references for the functions passed in as column config.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have an material table setup where one of the columns has a counter component to update the state of the table, this triggers a debounced update to the table data state, when profiling I noticed that there are two commits for the state change, one where only the data props change for the material table and another where the internal state for data, columns, orderByCollection, originalData, renderData, action changes. Can someone help me resolve to avoid re-mounting everything when the data changes on the component, what other areas can I look into, so far I have reduced the number of columns I am displaying to isolate the issue and also made sure I was passing stable references for the functions passed in as column config.
Beta Was this translation helpful? Give feedback.
All reactions