This example shows how to make a node behave as a connector instead of treating connectors as separate small handles only. That pattern is useful when the whole node, or a large region of it, should act like an interactive connection target.
It works well in compact editors, visual programming interfaces, and slot-based builders where dedicated tiny ports would make the UI harder to use. By letting the node itself participate in connection logic, you can keep the layout simpler without losing graph capabilities.
This is less about appearance and more about interaction design. Sometimes the best port is not a tiny port at all.
[component.html] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connectors/node-as-connector/node-as-connector.component.html [component.ts] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connectors/node-as-connector/node-as-connector.component.ts [component.scss] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connectors/node-as-connector/node-as-connector.component.scss [common.scss] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/_flow-common.scss
Use this approach when explicit micro-connectors make the product harder to understand or harder to operate.