Skip to content

refactor: reorganize components and update PromptComponent with priority attribute#8667

Merged
Yukiyukiyeah merged 74 commits into
mainfrom
fix-sidebar-refactor
Jun 27, 2025
Merged

refactor: reorganize components and update PromptComponent with priority attribute#8667
Yukiyukiyeah merged 74 commits into
mainfrom
fix-sidebar-refactor

Conversation

@edwinjosechittilappilly
Copy link
Copy Markdown
Collaborator

@edwinjosechittilappilly edwinjosechittilappilly commented Jun 22, 2025

Summary by CodeRabbit

  • New Features

    • Added priority setting to Prompt components, making them appear first in relevant lists or interfaces.
    • Introduced new sidebar categories: "Agents" and "Vector Stores", and added "Logic" and "Helpers" categories for improved navigation.
  • Enhancements

    • Renamed "I/O" sidebar category to "Input / Output" for clarity.
    • Updated display names for some components for better user understanding.
  • Bug Fixes

    • Standardized and reordered JSON fields in starter projects for consistency.
  • Chores

    • Updated internal imports to streamline component organization and improve maintainability.

@dosubot dosubot Bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Jun 22, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 22, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This update refactors component organization by removing the prompts package and relocating PromptComponent to the processing package. All references and imports are updated accordingly. The priority attribute is added to PromptComponent across code and starter projects. MCP-related components are reorganized under the agents package. Sidebar categories in the frontend are reordered and expanded.

Changes

File(s) Change Summary
.../components/agents/init.py, .../components/agents/mcp_component.py MCPToolsComponent imported/exported from agents; display name updated to "MCP Tools".
.../components/data/init.py MCPToolsComponent import/export removed from data package.
.../components/processing/init.py, .../components/processing/prompt.py PromptComponent imported/exported from processing; name updated to "Prompt Template"; priority attribute added.
.../components/processing/lambda_filter.py LambdaFilterComponent icon changed from "test-tube-diagonal" to "square-function".
.../components/prompts/init.py File deleted; PromptComponent no longer exported from prompts package.
.../initial_setup/starter_projects/*.json Added priority = 0 to embedded PromptComponent classes; minor key order/formatting adjustments in JSON.
.../initial_setup/starter_projects/basic_prompting.py, .../blog_writer.py, .../complex_agent.py, ... All imports of PromptComponent updated to reference processing package instead of prompts.
.../tests/integration/components/mcp/test_mcp_component.py, .../test_mcp_component.py MCPToolsComponent and related classes imported from agents instead of data.
.../tests/integration/components/output_parsers/test_output_parser.py, .../test_prompt.py, ... PromptComponent test imports updated to processing package.
.../tests/unit/graph/edge/test_edge_base.py, .../test_cycles.py, .../test_graph_state_model.py PromptComponent test imports updated to processing package.
.../tests/unit/initial_setup/starter_projects/test_memory_chatbot.py, .../test_vector_store_rag.py PromptComponent test imports updated to processing package.
src/frontend/src/utils/styleUtils.ts SIDEBAR_CATEGORIES reordered; new "Agents", "Vector Stores", "Logic", and "Helpers" categories added/rearranged.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant UI
    participant Backend
    participant PromptComponent
    participant MCPToolsComponent

    User->>UI: Selects component (Prompt or MCP Tools)
    UI->>Backend: Requests component details
    Backend->>PromptComponent: Accesses PromptComponent (now from processing)
    Backend->>MCPToolsComponent: Accesses MCPToolsComponent (now from agents)
    PromptComponent-->>Backend: Returns details (with priority attribute)
    MCPToolsComponent-->>Backend: Returns details (with updated display name)
    Backend-->>UI: Returns component info for sidebar/category display
Loading

Suggested labels

refactor, size:M, lgtm

Suggested reviewers

  • Yukiyukiyeah
  • ogabrielluiz
  • erichare
✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment
  • Commit Unit Tests in branch fix-sidebar-refactor

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot changed the title @coderabbitai refactor: reorganize components and update PromptComponent with priority attribute Jun 22, 2025
@github-actions github-actions Bot added the refactor Maintenance tasks and housekeeping label Jun 22, 2025
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (11)
src/backend/tests/unit/graph/graph/test_cycles.py (1)

8-8: Consistent import update for PromptComponent reorganization.

The import change is consistent with the component reorganization moving PromptComponent to the processing package.

This follows the same pattern as the previous test file and should be verified together with the other import updates.

src/backend/base/langflow/initial_setup/starter_projects/Financial Agent.json (1)

4227-4227: Duplicate: priority attribute added to PromptComponent
Same insertion applied to the second PromptComponent instance for consistent ordering.

src/backend/base/langflow/initial_setup/starter_projects/Sequential Tasks Agents.json (2)

1907-1973: Duplicate: ensure UI honors the new priority attribute.


2045-2107: Duplicate: ensure UI honors the new priority attribute.

src/backend/base/langflow/initial_setup/starter_projects/Research Agent.json (3)

808-808: Duplicate: priority attribute added
Same priority = 0 adjustment applied to the second PromptComponent instance.


1698-1698: Duplicate: priority attribute added
Same priority = 0 adjustment applied to the third PromptComponent instance.


1836-1836: Duplicate: priority attribute added
Same priority = 0 adjustment applied to the fourth PromptComponent instance.

src/backend/base/langflow/initial_setup/starter_projects/Instagram Copywriter.json (2)

937-937: Duplicate: priority insertion is consistent
This mirrors the change at line 654 and is applied correctly.


2087-2087: Duplicate: priority insertion is consistent
This mirrors the change at line 654 and is applied correctly.

src/backend/base/langflow/initial_setup/starter_projects/Text Sentiment Analysis.json (2)

733-733: Duplicate: priority attribute addition.
Same insertion of priority = 0 in a second PromptComponent snippet. Ensure consistency and that all instantiated components honor this new field.


879-879: Duplicate: priority attribute addition.
Third occurrence of adding priority = 0. Verify that every starter flow’s prompt ordering respects the new default priority.

🧹 Nitpick comments (1)
src/backend/base/langflow/initial_setup/starter_projects/Blog Writer.json (1)

216-216: Confirm correct priority usage
The new priority = 0 line correctly ensures this component appears first in ordering. Please verify this aligns with your component registry logic. For consistency with other class attributes, consider adding a type hint—e.g., priority: int = 0.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 15f4451 and 0385c80.

📒 Files selected for processing (47)
  • src/backend/base/langflow/components/agents/__init__.py (1 hunks)
  • src/backend/base/langflow/components/agents/mcp_component.py (1 hunks)
  • src/backend/base/langflow/components/data/__init__.py (0 hunks)
  • src/backend/base/langflow/components/processing/__init__.py (2 hunks)
  • src/backend/base/langflow/components/processing/lambda_filter.py (1 hunks)
  • src/backend/base/langflow/components/processing/prompt.py (1 hunks)
  • src/backend/base/langflow/components/prompts/__init__.py (0 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Basic Prompt Chaining.json (10 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Basic Prompting.json (3 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Blog Writer.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Custom Component Maker.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Diet Analysis.json (4 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Document Q&A.json (6 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Financial Agent.json (2 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Image Sentiment Analysis.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Instagram Copywriter.json (3 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Invoice Summarizer.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Meeting Summary.json (2 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Memory Chatbot.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Research Agent.json (4 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/SEO Keyword Generator.json (5 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/SaaS Pricing.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Sequential Tasks Agents.json (3 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Text Sentiment Analysis.json (3 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Twitter Thread Generator.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Vector Store RAG.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Youtube Analysis.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/basic_prompting.py (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/blog_writer.py (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/complex_agent.py (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/document_qa.py (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/hierarchical_tasks_agent.py (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/memory_chatbot.py (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/sequential_tasks_agent.py (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/vector_store_rag.py (1 hunks)
  • src/backend/tests/integration/components/mcp/test_mcp_component.py (1 hunks)
  • src/backend/tests/integration/components/output_parsers/test_output_parser.py (1 hunks)
  • src/backend/tests/integration/components/prompts/test_prompt.py (1 hunks)
  • src/backend/tests/integration/flows/test_basic_prompting.py (1 hunks)
  • src/backend/tests/unit/components/data/test_mcp_component.py (1 hunks)
  • src/backend/tests/unit/components/prompts/test_prompt_component.py (1 hunks)
  • src/backend/tests/unit/graph/edge/test_edge_base.py (1 hunks)
  • src/backend/tests/unit/graph/graph/test_cycles.py (1 hunks)
  • src/backend/tests/unit/graph/graph/test_graph_state_model.py (1 hunks)
  • src/backend/tests/unit/initial_setup/starter_projects/test_memory_chatbot.py (1 hunks)
  • src/backend/tests/unit/initial_setup/starter_projects/test_vector_store_rag.py (1 hunks)
  • src/frontend/src/utils/styleUtils.ts (1 hunks)
💤 Files with no reviewable changes (2)
  • src/backend/base/langflow/components/data/init.py
  • src/backend/base/langflow/components/prompts/init.py
🧰 Additional context used
🪛 Pylint (3.3.7)
src/backend/tests/unit/components/prompts/test_prompt_component.py

[error] 2-2: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/integration/flows/test_basic_prompting.py

[error] 2-2: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/integration/components/prompts/test_prompt.py

[error] 1-1: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/integration/components/output_parsers/test_output_parser.py

[error] 6-6: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/unit/graph/edge/test_edge_base.py

[error] 6-6: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/unit/graph/graph/test_graph_state_model.py

[error] 7-7: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/integration/components/mcp/test_mcp_component.py

[error] 9-9: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/unit/initial_setup/starter_projects/test_memory_chatbot.py

[error] 9-9: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/unit/graph/graph/test_cycles.py

[error] 8-8: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/unit/components/data/test_mcp_component.py

[error] 5-5: No name 'components' in module 'langflow'

(E0611)

src/backend/tests/unit/initial_setup/starter_projects/test_vector_store_rag.py

[error] 10-10: No name 'components' in module 'langflow'

(E0611)

🔇 Additional comments (72)
src/backend/base/langflow/components/processing/prompt.py (1)

14-15: Verify naming and ordering integration
Changing name to "Prompt Template" while display_name remains "Prompt" may affect serialization, registry lookups, or UI mappings. Also confirm that the new priority = 0 is handled by the component sorting logic and that other components have sensible default priorities.

src/backend/base/langflow/initial_setup/starter_projects/hierarchical_tasks_agent.py (1)

6-6: Import path updated
Nice work updating the import for PromptComponent to the new langflow.components.processing location.

src/backend/tests/integration/components/output_parsers/test_output_parser.py (1)

6-6: Import path updated
Confirmed the test now imports PromptComponent from langflow.components.processing.

src/backend/tests/integration/flows/test_basic_prompting.py (1)

2-2: Import path updated
The PromptComponent import has been correctly redirected to the processing package.

src/backend/base/langflow/initial_setup/starter_projects/sequential_tasks_agent.py (1)

5-5: Import path updated
Updated the import for PromptComponent to reflect its new package.

src/backend/base/langflow/initial_setup/starter_projects/complex_agent.py (1)

6-6: Import path update: Importing PromptComponent from langflow.components.processing correctly reflects the refactoring. The package’s processing/__init__.py now re-exports PromptComponent, so no further changes are needed here.

src/backend/tests/unit/graph/edge/test_edge_base.py (1)

6-6: Import path update in unit test: The test now imports PromptComponent from langflow.components.processing, matching the new module layout. This aligns with the refactoring and requires no additional adjustments.

src/backend/base/langflow/initial_setup/starter_projects/basic_prompting.py (1)

3-3: Import path update: Switching the PromptComponent import to langflow.components.processing correctly mirrors the removal of the old prompts package.

src/backend/tests/integration/components/prompts/test_prompt.py (1)

1-1: Import path update in integration test: The integration test import of PromptComponent from langflow.components.processing is consistent with the upstream refactoring.

src/backend/tests/unit/components/prompts/test_prompt_component.py (1)

2-2: Import path update in unit test: Importing PromptComponent from langflow.components.processing now matches the updated public API and requires no further edits.

src/backend/tests/unit/graph/graph/test_graph_state_model.py (1)

7-7: ```shell
#!/bin/bash

Check if PromptComponent is exported in the processing package init.py

grep -n "PromptComponent" src/backend/base/langflow/components/processing/init.py || echo "No direct export found"

echo "----- init.py content -----"
sed -n '1,200p' src/backend/base/langflow/components/processing/init.py


</details>
<details>
<summary>src/backend/tests/integration/components/mcp/test_mcp_component.py (1)</summary>

`9-9`: ```shell
#!/bin/bash
set -e

# List all package __init__.py files under langflow
echo "=== __init__.py files in langflow package ==="
find src/backend/base/langflow -type f -name "__init__.py"

# Show the beginning of the agents package __init__.py
if [ -f src/backend/base/langflow/components/agents/__init__.py ]; then
  echo -e "\n=== src/backend/base/langflow/components/agents/__init__.py ==="
  sed -n '1,200p' src/backend/base/langflow/components/agents/__init__.py
else
  echo -e "\nNo agents/__init__.py found."
fi

# Show the MCPToolsComponent definition
if [ -f src/backend/base/langflow/components/agents/mcp_component.py ]; then
  echo -e "\n=== src/backend/base/langflow/components/agents/mcp_component.py ==="
  sed -n '1,200p' src/backend/base/langflow/components/agents/mcp_component.py
else
  echo -e "\nNo mcp_component.py found in agents package."
fi
src/backend/base/langflow/initial_setup/starter_projects/blog_writer.py (1)

6-6: Clean import consolidation for processing components.

Consolidating the imports of ParserComponent and PromptComponent from the same processing package into a single import statement is cleaner and follows Python best practices.

src/backend/base/langflow/initial_setup/starter_projects/memory_chatbot.py (1)

4-4: Consistent PromptComponent import update.

The import change is consistent with the component reorganization pattern seen across all the reviewed files.

src/backend/tests/unit/initial_setup/starter_projects/test_memory_chatbot.py (1)

9-9: Import path updated correctly.

The import path change from langflow.components.prompts to langflow.components.processing aligns with the component reorganization described in the PR summary.

src/backend/base/langflow/components/processing/lambda_filter.py (1)

19-19: Improved icon semantic alignment.

The icon change from "test-tube-diagonal" to "square-function" better represents the component's function-related functionality.

src/backend/base/langflow/components/agents/mcp_component.py (1)

77-77: Display name improved for clarity.

The change from "MCP Connection" to "MCP Tools" better describes the component's functionality of providing access to MCP tools.

src/backend/tests/unit/components/data/test_mcp_component.py (1)

5-5: Import path updated for component relocation.

The import path correctly reflects the MCPToolsComponent relocation from the data package to the more appropriate agents package.

src/backend/base/langflow/initial_setup/starter_projects/vector_store_rag.py (1)

7-7: Import consolidation improves organization.

Consolidating the imports of ParserComponent and PromptComponent from the same processing package reduces import lines and improves code organization.

src/backend/base/langflow/initial_setup/starter_projects/document_qa.py (1)

4-4: Consolidate imports into new processing namespace.

The PromptComponent import has been merged into the existing processing import, reflecting the package refactor. Ensure no remaining imports reference langflow.components.prompts.

src/backend/base/langflow/components/processing/__init__.py (2)

17-17: Expose PromptComponent in processing package.

Adding PromptComponent import here makes it available under langflow.components.processing, aligning with the removal of the old prompts package.


42-42: Export PromptComponent via all.

Including "PromptComponent" in __all__ ensures it’s part of the public API for the processing components module.

src/backend/base/langflow/initial_setup/starter_projects/Invoice Summarizer.json (1)

216-216: Embed new priority attribute in PromptComponent code.

The inserted priority = 0 line in the code snippet will influence component ordering in the starter project. This update keeps the JSON embedding consistent with the updated component definition.

src/backend/base/langflow/initial_setup/starter_projects/Vector Store RAG.json (2)

649-649: Priority attribute addition looks correct.
Adding priority = 0 will ensure PromptComponent surfaces first in the UI ordering, matching the PR’s objective.


649-652: Let’s verify where process_prompt_template is defined and how it’s currently imported in the repo:

#!/bin/bash
# Locate the definition of process_prompt_template
rg --color=never -n "def process_prompt_template" -n

# Find all import occurrences to confirm the correct module path
rg --color=never -n "process_prompt_template" -n
src/backend/base/langflow/initial_setup/starter_projects/Blog Writer.json (1)

214-218: Inconsistent name attribute vs. refactoring summary
The embedded snippet still uses display_name = "Prompt" and name = "Prompt", but per the upstream refactor, this component should now be named "Prompt Template". Update both attributes here to match the new naming.

Likely an incorrect or invalid review comment.

src/backend/base/langflow/initial_setup/starter_projects/Image Sentiment Analysis.json (1)

883-884: Add priority attribute to PromptComponent
The priority = 0 line correctly sets the component ordering so prompts appear first. This matches the core refactor of PromptComponent and ensures consistency across starter projects.

src/backend/tests/unit/initial_setup/starter_projects/test_vector_store_rag.py (1)

9-11: Update import path for PromptComponent
Consolidating the import into langflow.components.processing reflects the relocation of PromptComponent. Tests now align with the new module structure.

src/backend/base/langflow/initial_setup/starter_projects/SaaS Pricing.json (1)

155-164: Confirm priority attribute insertion
You’ve correctly added priority = 0 to the PromptComponent class in this starter-project code snippet. Please verify that this matches the updated PromptComponent in processing/prompt.py and that the front-end respects the new priority ordering.

src/backend/base/langflow/initial_setup/starter_projects/Youtube Analysis.json (1)

1954-1954: To confirm the current definitions and usage of process_prompt_template and PromptComponent, let’s gather all references:

#!/bin/bash
# 1. All references to process_prompt_template
rg -n "process_prompt_template" .

# 2. All references to update_template_values
rg -n "update_template_values" .

# 3. All definitions of PromptComponent
rg -n "class PromptComponent" .
src/backend/base/langflow/initial_setup/starter_projects/Twitter Thread Generator.json (1)

1758-1758: Add priority attribute to PromptComponent
Including priority = 0 ensures the Prompt node appears first in starter flows. Verify this aligns with the backend PromptComponent implementation and that all other starter-project JSON files include the same change.

src/backend/base/langflow/components/agents/__init__.py (2)

2-2: Verify import of MCPToolsComponent
Importing MCPToolsComponent from .mcp_component matches its new location under agents. Ensure no residual references exist in the old data package.


4-4: Update all export list
Adding "MCPToolsComponent" makes the component publicly available via the agents package API. Confirm documentation and tests reflect this export.

src/backend/base/langflow/initial_setup/starter_projects/Financial Agent.json (1)

4055-4055: Add priority attribute to PromptComponent definition in starter JSON
The insertion of priority = 0 in the embedded code snippet ensures this component is ordered first in the playground, aligning with the PR objective.

src/backend/base/langflow/initial_setup/starter_projects/Memory Chatbot.json (1)

1210-1215: Confirm import path for process_prompt_template after refactor

The PromptComponent code embedded here still imports from langflow.base.prompts.api_utils. Since the prompts package was removed and components moved under processing, please verify this reference is accurate or adjust it to the new location (e.g. langflow.base.processing.api_utils).

src/backend/base/langflow/initial_setup/starter_projects/Custom Component Maker.json (2)

723-731: Priority attribute added correctly
The priority = 0 field is set to ensure this component appears first. This aligns with the pattern in other starter projects and should work as intended.


714-722: ```shell
#!/bin/bash
set -e

echo "Finding process_prompt_template definitions:"
rg -n "def process_prompt_template" -S .

echo
echo "Locating all api_utils.py files:"
fd api_utils.py

echo
echo "Locating processing/api_utils.py if present:"
fd processing/api_utils.py

echo
echo "Finding PromptInput class definitions:"
rg -n "class PromptInput" -S .

echo
echo "Finding DefaultPromptField class definitions:"
rg -n "class DefaultPromptField" -S .


</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/Sequential Tasks Agents.json (1)</summary>

`1722-1783`: **Validate that the new `priority` field is honored by the UI renderer.**

You’ve added `priority = 0` to the PromptComponent in this starter project to push it to the top. Please confirm that the frontend logic reads and sorts nodes by this `priority` attribute (including zero‐based priorities) so this change actually affects display order.

</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/Research Agent.json (1)</summary>

`355-355`: **Add explicit priority attribute to PromptComponent**  
The `priority = 0` line ensures this prompt component is displayed first in the UI, standardizing ordering across all starter projects.

</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/Instagram Copywriter.json (1)</summary>

`654-654`: **Add `priority` attribute to prompt component**  
The new `priority = 0` line is correctly inserted in the `PromptComponent` definition to enforce ordering.

</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/Meeting Summary.json (2)</summary>

`1087-1087`: **Add `priority` attribute to PromptComponent (first instance)**  
The embedded `PromptComponent` now includes `priority = 0`, ensuring it appears first in the UI and matching the pattern used in other starter projects.

---

`2536-2536`: **Add `priority` attribute to PromptComponent (second instance)**  
The second occurrence of `PromptComponent` also has `priority = 0` added for consistent component ordering across this flow.

</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/Text Sentiment Analysis.json (1)</summary>

`585-585`: **Add `priority` attribute to PromptComponent.**
Including `priority = 0` in the embedded `PromptComponent` ensures this node is surfaced first in flows. Confirm that the front-end ordering logic reads and applies this attribute correctly.

</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/Document Q&A.json (6)</summary>

`415-416`: **Standardize JSON key ordering for ChatInput node**  
Reordered `selected_output` before `type` to align with other node entries. This is a purely cosmetic change; JSON key order does not affect behavior.

---

`1033-1034`: **Standardize JSON key ordering for File node**  
Moved `selected_output` ahead of `type` for consistency across node definitions. No functional impact.

---

`1147-1147`: **Add `priority` attribute to PromptComponent**  
Introduced `priority = 0` to ensure the Prompt component surfaces first in the UI. Verify that the component‐ordering logic consumes this new field as intended.

---

`1191-1192`: **Standardize JSON key ordering for Prompt node**  
Swapped `selected_output` and `type` keys to match the established pattern in other nodes. No runtime change.

---

`1586-1588`: **Standardize JSON key ordering for OpenAIModel node**  
Reordered `selected_output` before `type` for uniformity. This update is cosmetic only.

---

`1761-1763`: **Standardize JSON key ordering for Parser node**  
Adjusted the order of `selected_output` and `type` to remain consistent across node definitions.

</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/Basic Prompting.json (3)</summary>

`385-387`: **Consistent JSON key ordering**  
Reordered `"selected_output"` above `"type"` in the ChatInput node for structural consistency. No functional change.

---

`469-469`: **Added `priority` attribute to PromptComponent**  
The embedded PromptComponent class now includes `priority = 0` to explicitly control its ordering. This aligns with other components in starter projects.

---

`516-517`: **Consistent JSON key ordering**  
Reordered `"selected_output"` above `"type"` in the Prompt node for consistency with other nodes.

</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/SEO Keyword Generator.json (4)</summary>

`161-161`: **Added `priority` attribute to PromptComponent**  
The PromptComponent class in the SEO Keyword Generator now declares `priority = 0` to standardize its position among other components.

---

`344-345`: **Consistent JSON key ordering**  
Moved `"selected_output"` above `"type"` in the first Prompt node to align with JSON structure conventions.

---

`463-463`: **Added `priority` attribute to PromptComponent**  
Second PromptComponent class now includes `priority = 0` for uniform component ordering across projects.

---

`509-510`: **Consistent JSON key ordering**  
Reordered `"selected_output"` above `"type"` in the second Prompt node for consistency.

</details>
<details>
<summary>src/frontend/src/utils/styleUtils.ts (2)</summary>

`208-208`: **Improved clarity in display name.**

The change from "I/O" to "Input / Output" provides better clarity for users who may not be familiar with the "I/O" abbreviation.

---

`209-219`: **Well-organized sidebar category restructuring.**

The reorganization follows a logical hierarchy:
1. Core components (Saved, Input/Output) remain at the top
2. Advanced functionality (Agents, Vector Stores, Logic, Helpers) is grouped together
3. Basic I/O components (Inputs, Outputs, Prompts) are positioned after the advanced categories

This structure aligns with the backend component reorganization mentioned in the AI summary and improves user experience by grouping related functionality.

</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/Diet Analysis.json (4)</summary>

`386-388`: **Proper JSON structure for node configuration.**

The addition of the `"selected_output"` field as a standalone key alongside `"type"` and `"showNode"` ensures proper node configuration structure in the ChatInput component.

---

`471-471`: **Component priority standardization.**

The addition of `priority = 0` to the PromptComponent class aligns with the component reorganization described in the AI summary. This ensures consistent ordering across starter projects without affecting the component's functionality.

---

`517-519`: **Consistent node configuration structure.**

Similar to the ChatInput component, adding the `"selected_output"` field ensures proper JSON structure for the Prompt node configuration.

---

`893-895`: **Completed node configuration standardization.**

The addition of `"selected_output"` field to the NovitaModel node completes the structural consistency across all nodes in this starter project.

</details>
<details>
<summary>src/backend/base/langflow/initial_setup/starter_projects/Basic Prompt Chaining.json (10)</summary>

`259-259`: **Add `priority` attribute to PromptComponent code string**  
The embedded PromptComponent definition now includes `priority = 0`, which correctly enforces its display order.

---

`304-305`: **Include `selected_output` and `type` for Prompt-4IOgm node**  
Defining `"selected_output": "prompt"` and `"type": "Prompt"` ensures the correct default output and component type are wired in the flow.

---

`602-603`: **Set `selected_output` and `type` for ChatInput-GyBUF node**  
Adding `"selected_output": "message"` and `"type": "ChatInput"` aligns this node’s metadata with its outputs.

---

`990-990`: **Add `priority` attribute to PromptComponent code string (Prompt-FRjO8)**  
The code string for Prompt-FRjO8 now includes `priority = 0`, matching the intended ordering behavior.

---

`1035-1036`: **Include `selected_output` and `type` for Prompt-FRjO8 node**  
Specifying `"selected_output": "prompt"` and `"type": "Prompt"` ensures the correct wiring in the chaining sequence.

---

`1119-1119`: **Add `priority` attribute to PromptComponent code string (Prompt-f1f2v)**  
The code string for Prompt-f1f2v now includes `priority = 0`, consistently prioritizing all Prompt components.

---

`1164-1165`: **Include `selected_output` and `type` for Prompt-f1f2v node**  
Defining `"selected_output": "prompt"` and `"type": "Prompt"` keeps this node’s output configuration consistent.

---

`1633-1635`: **Add `selected_output` and `type` for OpenAIModel-lL9HA node**  
Setting `"selected_output": "text_output"` and `"type": "OpenAIModel"` establishes the correct default output and node type.

---

`2023-2025`: **Add `selected_output` and `type` for OpenAIModel-JieGw node**  
Defining `"selected_output": "text_output"` and `"type": "OpenAIModel"` ensures this model node is configured correctly in the flow.

---

`2413-2415`: **Add `selected_output` and `type` for OpenAIModel-dXMRv node**  
Specifying `"selected_output": "text_output"` and `"type": "OpenAIModel"` aligns the node’s metadata with its outputs.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

@github-actions github-actions Bot added refactor Maintenance tasks and housekeeping and removed refactor Maintenance tasks and housekeeping labels Jun 23, 2025
Copy link
Copy Markdown
Member

@Cristhianzl Cristhianzl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@dosubot dosubot Bot added the lgtm This PR has been approved by a maintainer label Jun 23, 2025
@github-actions github-actions Bot added refactor Maintenance tasks and housekeeping and removed refactor Maintenance tasks and housekeeping labels Jun 23, 2025
@github-actions github-actions Bot added refactor Maintenance tasks and housekeeping and removed refactor Maintenance tasks and housekeeping labels Jun 23, 2025
@github-actions github-actions Bot added refactor Maintenance tasks and housekeeping and removed refactor Maintenance tasks and housekeeping labels Jun 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fast-track Skip tests and sends PR into the merge queue lgtm This PR has been approved by a maintainer refactor Maintenance tasks and housekeeping size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants