Provide `route` name in `direct` node's label

[lordrip]

Please describe the feature that you want to propose

In the case of a direct node, it would be beneficial to see the actual route name in the label.

In the following screenshot, the name's property value is start2, then the label could be direct: start2

[lhein]

Just keep in mind that this is not the route name but the destination name for the direct endpoint. Your first route could for instance end with a direct endpoint called msgBox and then when defining your next new route you could start with another direct endpoint with the same name msgBox which would basically connect both routes. For such cases it would also make sense to pre-populate the name field (as drop down with direct edit capabilities) with all found direct endpoint names over all the routes. (consolidated to only have unique names) In a next step we could draw a connection between connected routes.

- route:
    id: route-1552
    from:
      id: from-3735
      uri: direct
      parameters:
        name: msgBox
      steps:
        - log:
            id: log-3963
            message: template message
- route:
    id: route-1607
    from:
      id: from-3857
      uri: timer
      parameters:
        period: "1000"
        timerName: template
      steps:
        - log:
            id: log-2780
            message: template message
        - to:
            id: to-6598
            uri: direct
            parameters:
              name: msgBox

[lordrip]

Raising the priority since it's a enhancement for visualization purposes

[lhein]

Can we create a function that takes a step and then decides what to display individually for each step. Additionally whenever a "description" has been provided for a step, we should use the description instead.

[lordrip]

Yes, we have it already, it's here, it's just a matter of extending it to provide more tailored information.