Foblex Flow
Introduction
Overview
Nodes
Custom Nodes
Drag Handle
Node Selection
Resize Handle
Rotate Handle
Grouping
Drag to Group
Connectors
Node as Connector
Connector Inside Node
Connector Outlet
Limiting Connections
Connection Rules
Connectable Side
Updated
Connections
Drag to Connect
Drag to Reassign
Create Node on Connection Drop
Remove Connection on Drop
Assign Node to Connection on Drop
Auto Snap
Connection Types (Straight, Segment, Bezier, Adaptive Curve)
Custom Connection Type
Connection Behaviours
Connection Markers
Connection Content
Updated
Connection Waypoints
New
Connection Gradients
Updated
Connection Connectable Side
New
Extensions
Auto Pan
New
Add Node from Palette
Selection Area
Help in Positioning (Legacy)
Deprecated
Magnetic Lines
New
Magnetic Rects
New
Grid System
Minimap
Zoom
Background
Plugins
Dagre Layout
New
Dagre Auto Layout
New
ELK.js Layout
New
ELK.js Auto Layout
New
Advanced
Large Scene Performance
Connection Redraw Performance
Updated
Cut/Copy/Paste
Undo/Redo
Undo/Redo V2
Drag Start/End Events
Custom Event Triggers
Reference Apps
AI Low-Code Platform
Updated
Schema Designer
Updated
Call Center Flow
Updated
UML Diagram
Updated
Tournament Bracket
Updated
Foblex Flow

Connection Connectable Side

Description

Control which side an individual connection uses at both ends instead of relying only on connector defaults. Use this when routing should stay predictable, or when a specific edge needs to override the usual node-side behavior.

Example

[example.html] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/libs/f-examples/connections/connection-connectable-side/example.html [example.ts] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/libs/f-examples/connections/connection-connectable-side/example.ts [example.scss] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/libs/f-examples/connections/connection-connectable-side/example.scss

Supported modes

  • Set explicit sides such as LEFT, RIGHT, TOP, or BOTTOM.
  • Use CALCULATE, CALCULATE_HORIZONTAL, or CALCULATE_VERTICAL when the route should adapt to node positions.
  • Configure the side independently for the output and input of each connection.

Why it matters

  • Manual mode helps when the route itself carries meaning and should not jump around.
  • Calculated modes are useful when layouts are dynamic but still need cleaner edge directions.
  • Connection-side settings take precedence over connector-side settings, so they are the stronger routing control.
Edit this page on GitHub