destroy old graph when new model has a new graph id #4882
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes:
Fixes: https://issues.redhat.com/browse/ODC-3451
Analysis / Root cause:
The topology Visualization never cleaned up the old graph element reference if a new model was set with the graph having a new ID. Since IDs define element object identify in a visualization, a new graph element is created with the new ID. Therefore the old graph is no longer needed however it wasn't properly disposed.
Solution Description:
Check if model contains a new graph ID and if so dispose of the old graph.
Removed the
key
from withinPipelineTemplate
which was a temporary fix.Added test case for this
Screen shots / Gifs for design review:
Browser conformance: