feat(agentFlow) - Add support for listFlows#6005
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces the capability to list various types of flows (chatflows, agentflows) within the application. By integrating the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces support for listFlows to fetch chatflows and agentflows. The changes are well-implemented, including a new listFlows method in the loadMethodRegistry, wiring up the chatflowsApi in the useAsyncOptions hook, and adding comprehensive unit tests. The code is solid and well-tested. I have one suggestion to improve code readability and maintainability, particularly concerning the clarity of conditional logic.
packages/agentflow/src/infrastructure/api/loadMethodRegistry.ts
Outdated
Show resolved
Hide resolved
| */ | ||
| function getChatflowTypeLabel(type: string | undefined): string { | ||
| if (type === 'AGENTFLOW') return 'Agentflow V2' | ||
| if (type === 'MULTIAGENT') return 'Agentflow V1' |
There was a problem hiding this comment.
nit: are these shown on the UI? might be good to use a const map or use switch but given we only have 3 types right now it's fine to keep current implementation.

FLOWISE-266
Added listFlows to the registry via chatflowsApi.getAllChatflows(),wired chatflowsApi into ApiServices and useAsyncOptions
Added test cases for chatFlows
listFlows.mov