Michał Korczak I totally agree this isn't needed for most users and therefore shouldn't be priorized. Other components more requested should come first.

But I can totally see this as a state machine. In fact, very similar to the Draggable component sage has been building in live streams.

Imagine this: a trigger that changes the state from "idle" to "connecting". Once in connecting, we listen to mousemove events to update the position (to style the arrow), and pressing esc or maybe even right clicking to cancel. Then we listen for clicks on the target to change the state from "connecting" to "connected". Once connected, we could show a RemoveTrigger, to remove the connection and change the state back to "idle"

and I'm just scratching the surface here, a component like ths could have several states to handle logic like connecting N to N entities.

But I totally understand if the core team decides not to do this, it was just a cool idea that passed in my mind and I wanted to share here :)

Filipe Pfluck I see. I think it's a complicated thing anyway. Should it be used on canvas like in the editor you referenced?