topics with same name but different type are shown as the same topic

[ottojo]

If publishers/subscribers of different type exist for the same topic name, they are not connected, but are shown as such in the node graph.

Showing them as disconnected or highlighting the topic would be helpful for debugging, assuming this is a rare and usually undesired configuration. (Which might occur for example while moving from Twist to TwistStamped while migrating to Jazzy...)

jonasotto@ade ➜  workspace ros2 topic info /joy_teleop/cmd_vel -v
Type: ['geometry_msgs/msg/Twist', 'geometry_msgs/msg/TwistStamped']

Publisher count: 1

Node name: teleop_twist_joy_node
Node namespace: /joy_teleop
Topic type: geometry_msgs/msg/TwistStamped
Topic type hash: RIHS01_5f0fcd4f81d5d06ad9b4c4c63e3ea51b82d6ae4d0558f1d475229b1121db6f64
Endpoint type: PUBLISHER
GID: 01.0f.38.ef.b6.f2.fd.ea.00.00.00.00.00.00.15.03
QoS profile:
  Reliability: RELIABLE
  History (Depth): UNKNOWN
  Durability: VOLATILE
  Lifespan: Infinite
  Deadline: Infinite
  Liveliness: AUTOMATIC
  Liveliness lease duration: Infinite

Subscription count: 1

Node name: twist_mux
Node namespace: /
Topic type: geometry_msgs/msg/Twist
Topic type hash: RIHS01_9c45bf16fe0983d80e3cfe750d6835843d265a9a6c46bd2e609fcddde6fb8d2a
Endpoint type: SUBSCRIPTION
GID: 01.0f.38.ef.b8.f2.4a.f9.00.00.00.00.00.00.14.04
QoS profile:
  Reliability: BEST_EFFORT
  History (Depth): UNKNOWN
  Durability: VOLATILE
  Lifespan: Infinite
  Deadline: Infinite
  Liveliness: AUTOMATIC
  Liveliness lease duration: Infinite