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
{{ message }}
This repository was archived by the owner on Dec 5, 2024. It is now read-only.
fix: referenceNode memory leak in Manager (#312) (#313)
* fix: referenceNode memory leak
Instead of storing referenceNode in state, store it in a class property. This is done to enable the component to cleanup referenceNode’s value during unmounting.
I also added unit tests to account for this change, but that resulted in me having to update some dependencies and snapshots to get unit tests to pass.
* CR: Create separate setter and getter contexts
In order to help reduce re-renders of the Reference component, this commit creates separate context objects for the setters and getters of the referenceNode attribute.
This also removes the need for a context object, so it simplifies the management of the referenceNode attribute in the Manager class.
* CR Feedback: remove need for componentWillUnmount
* FIx flow
* Update size snapshot
0 commit comments