-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can langflow support multiple output? #1532
Comments
Hey there @mcathena! Nice to see you back in the orbit of Langflow questions. Hope you've been doing stellar since our last chat! 🌟 Based on the information available, it seems that the current version of langflow (v0.6.10) does not explicitly support multiple outputs for a single node. However, the codebase does contain functionality that could potentially be adapted to support this feature. The Moreover, the use of a custom node type ( // Assuming GenericNode is a functional component that renders a node
const GenericNode = ({ data }) => {
return (
<div>
{/* Node content here */}
<div>Node ID: {data.id}</div>
{/* Example of multiple output handles */}
<Handle type="source" position={Position.Right} id="a" />
<Handle type="source" position={Position.Right} id="b" />
</div>
);
}; In this example, two handles (outputs) are added to the As for your question about future development plans, I found a similar open issue titled [Feature Request] Conditional Logic and Branching Pipelines which was last updated on March 13, 2024. This issue suggests that there is interest in developing functionality that could potentially include support for multiple outputs per node. However, without further information or updates from the repository maintainers, it's difficult to say for certain whether this feature will be implemented. I hope this information is helpful. If you have any further questions or need clarification, please don't hesitate to ask. Sources
|
I'd like to assign multiple output that can connect to different nodes with condition. Are we planning to develop this functionality?
The text was updated successfully, but these errors were encountered: