This example shows how to create a node when a dragged connection is dropped into empty space. Instead of failing the gesture or forcing the user to open a separate add-node flow first, the editor can turn that unfinished connection into a new step.
This interaction is a strong fit for workflow builders, AI orchestration tools, and internal low-code products because it keeps graph editing fast and sequential. Users can think in terms of "connect to the next step" and create that step only when they need it.
It is one of the patterns that makes a node editor feel product-like rather than demo-like.
[component.html] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connections/create-node-on-connection-drop/create-node-on-connection-drop.component.html [component.ts] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connections/create-node-on-connection-drop/create-node-on-connection-drop.component.ts [component.scss] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connections/create-node-on-connection-drop/create-node-on-connection-drop.component.scss [common.scss] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/_flow-common.scss
This example focuses on drop handling, node creation, and keeping the edge creation flow intuitive.