Open pawelbaran opened 3 years ago
I cannot make Dynamo crash repeating the step above but I do get the issue with mismatched inputs. The problem is on the CustomObject component itself (as confirmed by the ToJson and new Explode components), not on the Explode. Although I don't know why Explode also complains. I will have a look.
After spending some time with this, I still don't know how to fix it.
Dynamo itself passes the wrong inputs to BuildOutputAst
once the user has removed an input. A copy/pasted component is corrected and works fine though so there must be some command we can send Dynamo to properly fix this. After trying a few things like MarxkComponentAsModified
without success I decided this is something I am not happy to spend more time on right now so it will have to wait. Thankfully this is a bug that has a few ways to get around so I guess Dynamo users are used to have to do that.
Description:
After removing one of the
CustomObject
properties and trying to update outputs of theExplode
component, Dynamo crashes:After removing one of the
CustomObject
properties and replacing theExplode
component, output names do not match the values: