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
This is rarely a problem because tables tend to be contained by other unique component instances (like pages), but as we move from manual component creation to DSLs and helper functions it's likely we'll end up with two pages with the same component structure. This could prevent React from remounting these components leading to issues with stale component state. For coincidences like these it might be a good idea to have the Table component reset itself when its identifying name changes to prevent mixing up localStorage data.
The text was updated successfully, but these errors were encountered:
This is rarely a problem because tables tend to be contained by other unique component instances (like pages), but as we move from manual component creation to DSLs and helper functions it's likely we'll end up with two pages with the same component structure. This could prevent React from remounting these components leading to issues with stale component state. For coincidences like these it might be a good idea to have the Table component reset itself when its identifying name changes to prevent mixing up localStorage data.
The text was updated successfully, but these errors were encountered: