-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Environment:OS:
node.js / npm versions:
Additional info:
Problem Statement/Rationale
Steps to Reproduce
This one is hard to reproduce as it does not happen consistently, it can oftentimes be caused by:
- Click on a node in the diagram
- Change the collection name
- Blur the input (which submits the change) by clicking in an empty space in the diagram (this closes the sidebar).
- Click back on the node.
Expected Results
I expect the node to be updated and the update to be rendered without problems.
Actual Results
Sometimes this node starts disappearing, and eventually we reach a ResizeObserver error. The video attached shows a larger collection and a node with a longer name. This is how I was able to reproduce it locally, but the e2e tests repeatedly run into the ResizeObserver error with mere 2 collections and short names.
Additional information
The problem is likely due to the react flow library attempting several re-renders at once. One idea is to try using different ids (atm we use namespace - the object of change here - as an id for the node).
- related to
-
COMPASS-9737 Adding too many nodes too fast leads to failure
-
- Closed
-
-
COMPASS-9877 Update how node and field interactions are passed and used in diagramming
-
- Closed
-