Manually shape connection routes by adding interactive waypoints between nodes. Use this when users need cleaner edge routing without giving up control of the underlying waypoint data in your application state.
[component.html] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connections/connection-waypoints/connection-waypoints.html [component.ts] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connections/connection-waypoints/connection-waypoints.ts [component.scss] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/connections/connection-waypoints/connection-waypoints.scss [common.scss] <<< https://raw.githubusercontent.com/Foblex/f-flow/main/projects/f-examples/_flow-common.scss
[(waypoints)] to your own state and react through (fConnectionWaypointsChanged).Place <f-connection-waypoints> inside <f-connection> and configure:
[(waypoints)] for two-way binding with your waypoint array.radius for the visual size of candidates and active waypoints.The feature stays data-driven: Foblex Flow handles interaction, but the waypoint array still belongs to your app.