the display name of nodes can sometimes be incoherent, when some features that generate the displayName very verbosely, maybe in workflows that are very dynamic it'd be preferable if the user could choose create their own logic for the displayName.
Use Cases
Use cases include anyone using withParam on an array of a complex datatype.
currently the names of withParam nodes is set by the value corresponding to the node in the array, for arrays with complex datatypes, this introduces visual clutter without benefitting workflow readability.
I think that if withParam (or in general, even) you could separate the display name from the template name, and making the display name something that can be dynamically defined, you could make the workflow page in the UI more understandable
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
Summary
the display name of nodes can sometimes be incoherent, when some features that generate the displayName very verbosely, maybe in workflows that are very dynamic it'd be preferable if the user could choose create their own logic for the displayName.
Use Cases
Use cases include anyone using withParam on an array of a complex datatype.
currently the names of withParam nodes is set by the value corresponding to the node in the array, for arrays with complex datatypes, this introduces visual clutter without benefitting workflow readability.
I think that if withParam (or in general, even) you could separate the display name from the template name, and making the display name something that can be dynamically defined, you could make the workflow page in the UI more understandable
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.