You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using @foblex/flow with ELK.js for workflow diagram layout. The official example applies ELK's node positioning, but doesn't show how to utilize the edge path data provided in ELK's layout results.
For FConnectionComponent, it didn't expose fpath. For Custom Connection Type, IFConnectionBuilderRequest only provide the source and target position.
Could you provide guidance on how to properly consume ELK's generated edge paths?
This discussion was converted from issue #146 on July 24, 2025 16:25.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using @foblex/flow with ELK.js for workflow diagram layout. The official example applies ELK's node positioning, but doesn't show how to utilize the edge path data provided in ELK's layout results.
For FConnectionComponent, it didn't expose fpath. For Custom Connection Type, IFConnectionBuilderRequest only provide the source and target position.
Could you provide guidance on how to properly consume ELK's generated edge paths?
Beta Was this translation helpful? Give feedback.
All reactions