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
Describe the bug
I notice that when I delete an edge or a node there is still a corresponding react element in react extension's Components view (or whatever you call it). It seems that you remove dom elements but you never call ReactDOM.unmountComponentAtNode. Is it on purpose? Isn't pretty much a memory leak? I could be wrong, so please explain why it's done this way.
To Reproduce
Steps to reproduce the behavior:
Remove a node or an edge
Look into react extension's Component sview
Notice that there are still components "alive"
Expected behavior
They should be removed, I guess?
Screenshots
Notice the NaNpx (an edge was removed, but the React component still exists?)
Desktop (please complete the following information):
OS: [e.g. iOS] macOs
Browser [e.g. chrome, safari] firefox/chrome
Version [e.g. 22] newest
Additional context
version 8.0.0-beta.6
node v14.17.0
The text was updated successfully, but these errors were encountered:
Describe the bug
I notice that when I delete an edge or a node there is still a corresponding react element in react extension's Components view (or whatever you call it). It seems that you remove dom elements but you never call
ReactDOM.unmountComponentAtNode
. Is it on purpose? Isn't pretty much a memory leak? I could be wrong, so please explain why it's done this way.To Reproduce
Steps to reproduce the behavior:
Expected behavior
They should be removed, I guess?
Screenshots
Notice the NaNpx (an edge was removed, but the React component still exists?)
Desktop (please complete the following information):
Additional context
version 8.0.0-beta.6
node v14.17.0
The text was updated successfully, but these errors were encountered: