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
This might not be immediately easy to fix. But now that the property renaming has been fixed in the visual editor (thanks, @paullewis), would it be possible to update the ports the edges are wired to when a property name is updated?
e.g.
input.foo -> output.bar
rename foo to baz
The schema is updated
The input node will still have the input.foo -> output.bar edge connecting a no longer fulfilled property.
Ideally, when a property is renamed and is already connected to edges, it would be nice for any associated edges to have the ports they're connected to updated.
This may be suitable for a toggleable "sync port renames" setting, as I can imagine people wanting both behaviours.
The text was updated successfully, but these errors were encountered:
I really like the setting suggestion, because on the surface this is a duplicate of #930. I'll have a ponder, but yeah my hunch is that we'd need to update the port names to match as part of a multi-edit, and that seems doable.
This might not be immediately easy to fix. But now that the property renaming has been fixed in the visual editor (thanks, @paullewis), would it be possible to update the ports the edges are wired to when a property name is updated?
e.g.
input.foo
->output.bar
foo
tobaz
input.foo
->output.bar
edge connecting a no longer fulfilled property.Ideally, when a property is renamed and is already connected to edges, it would be nice for any associated edges to have the ports they're connected to updated.
This may be suitable for a toggleable "sync port renames" setting, as I can imagine people wanting both behaviours.
The text was updated successfully, but these errors were encountered: