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
One could call forceUpdate just on the updated mounted instances. This way the amount of calls to render would be minimized and (more importantly) the reference to the root of the tree would become unnecessary.
I tried adding these lines at #createClassProxy.js:176 (branch 2.0.8) and it seems to work fine:
One could call forceUpdate just on the updated mounted instances. This way the amount of calls to render would be minimized and (more importantly) the reference to the root of the tree would become unnecessary.
I tried adding these lines at #createClassProxy.js:176 (branch 2.0.8) and it seems to work fine:
(code adapted from react-deep-force-update)
and seems to be a tiny bit faster.Update:
I tested it in a real project: up to 5 times faster, no issues found, no react router warnings anymore.
The text was updated successfully, but these errors were encountered: