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
When replacing nodes on the canvas it sometimes happens that the original node isn't replaced but the replacement gets appended to the original node. (see video)
The text was updated successfully, but these errors were encountered:
…t work
Currently, there's a piece of logic that checks if the node meant to be replaced has a single
`step` property that can have children. This logic was causing that for some special nodes,
like `doCatch`, the replace step functionality didn't work, and the intended replacement
step gets appended instead.
The fix is to remove said functionality as it was already implemented in a different manner.
Fixes: KaotoIO#370
When replacing nodes on the canvas it sometimes happens that the original node isn't replaced but the replacement gets appended to the original node. (see video)
The text was updated successfully, but these errors were encountered: