This example shows how to limit the number of connections that a connector, port, or node can accept. Connection limits are one of the simplest ways to keep a graph editor aligned with product rules instead of allowing arbitrary wiring.
That is important in workflow builders, API mappers, and logic tools where one input may accept only one source, while another port may support many outbound connections. Without guardrails, users can create invalid states that are harder to explain and harder to repair.
A clear connection limit usually improves UX because it makes the editor behave like the product domain, not like a blank canvas.
[component.html] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connectors/limiting-connections/limiting-connections.component.html [component.ts] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connectors/limiting-connections/limiting-connections.component.ts [component.scss] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connectors/limiting-connections/limiting-connections.component.scss [common.scss] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/_flow-common.scss
This example is a good starting point when your nodes need structural rules, not just visual freedom.