# [RFC] Unified fConnector instead of fInput / fOutput — what do you think?

[siarheihuzarevich]

Hey everyone! 👋

I’m planning to simplify the Foblex Flow API by removing the old fInput and fOutput directives and replacing them with a single, more flexible directive — fConnector.

---

🧠 Why

I recently added support for reassigning connections from both ends — not just the target side. This made the distinction between fInput and fOutput much less relevant.

You can now define the behavior using inputs instead of separate directives.

---

✅ New API

Here’s what the new fConnector looks like:

<!-- Input only -->
<div fConnector mode="target"></div>

<!-- Output only -->
<div fConnector mode="source"></div>

<!-- Both input and output (default) -->
<div fConnector></div>

You can also control the side and direction:

<div fConnector mode="source" fConnectableSide="right"></div>

And disable connection logic:

<div fConnector mode="target" [disabled]="true"></div>

🔄 What will happen

• fInput and fOutput will be removed in the next major release
• All functionality will be supported via fConnector
• Docs and examples will be updated accordingly

❓ Question

Do you rely on the clear separation of fInput and fOutput in your templates?
Or does this unified version look cleaner and more useful to you?
Let me know your thoughts — especially before I remove the legacy directives! 💬

[relliv]

Is this update will provide more flexibility. For example, is if I move a node from left to right connection will move opposite/closest side? Today I was thinking about current fix position experience. Fixed connection sides/input/output is not cover more possibilities. Yes current solution is fit for some designs but in my case everything is look messy. I think floating connection sides/points will improve visual satisfaction.

Example from jsplumb library.

Screen.Recording.2025-07-27.at.02.28.08.mov

[siarheihuzarevich]

I'll try to do this, but I'll ask you to create a separate feature request for this

[relliv]

Sure. I think unified unified API will be understand easier. But we can see side effects in real world projects because there could be multiple fNodeInput/fNodeOutput implementation in same node.

[JPotel38]

Hello, I would be a very good improvement ! Do you know when it will be live ? 😄
Many thanks !

[siarheihuzarevich]

@JPotel38 June 2026

[JPotel38]

Alright, thanks 😄