Skip to content

docs: Add more detail to some template notes#9230

Merged
edwinjosechittilappilly merged 9 commits into
mainfrom
lfoss-1556-2
Aug 1, 2025
Merged

docs: Add more detail to some template notes#9230
edwinjosechittilappilly merged 9 commits into
mainfrom
lfoss-1556-2

Conversation

@aimurphy
Copy link
Copy Markdown
Collaborator

@aimurphy aimurphy commented Jul 29, 2025

Added more detail and updated some template notes before removing the template pages from the main docs.

Summary by CodeRabbit

  • Documentation
    • Improved and clarified the descriptive text in starter project guides, offering more detailed explanations, updated quickstart instructions, and clearer usage notes for Basic Prompting, Financial Report Parser, Memory Chatbot, Sequential Tasks Agents, Travel Planning Agents, and Vector Store RAG templates. These updates enhance user understanding and onboarding for each starter project.

@aimurphy aimurphy self-assigned this Jul 29, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 29, 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 change updates the descriptive README note content in six starter project JSON files within the initial setup directory. The updates revise, expand, and clarify documentation for each flow, providing improved explanations, usage instructions, and context for users. No structural, functional, or code-level changes are introduced.

Changes

Cohort / File(s) Change Summary
Basic Prompting Documentation Update
src/backend/base/langflow/initial_setup/starter_projects/Basic Prompting.json
Expanded and clarified the note node description, providing more detailed instructions, explanations of prompt templates, variable usage, and next steps for experimentation.
Financial Report Parser Documentation Update
src/backend/base/langflow/initial_setup/starter_projects/Financial Report Parser.json
Condensed and simplified the note node description, generalizing API key/model instructions, merging component explanations, and removing markdown formatting for a clearer, more concise overview.
Memory Chatbot Documentation Update
src/backend/base/langflow/initial_setup/starter_projects/Memory Chatbot.json
Revised the note node description to clarify the flow's purpose, update quickstart steps, and add a section explaining the Message History component's role and usage, including a link to documentation.
Sequential Tasks Agents Documentation Update
src/backend/base/langflow/initial_setup/starter_projects/Sequential Tasks Agents.json
Replaced the markdown-formatted README note with a concise, structured description, clarified API key setup, provided explicit quickstart steps, and emphasized financial query instructions and template adaptability.
Travel Planning Agents Documentation Update
src/backend/base/langflow/initial_setup/starter_projects/Travel Planning Agents.json
Updated the note node description to clarify agent roles, flow structure, and user interaction, while retaining the original quickstart steps.
Vector Store RAG Documentation Update
src/backend/base/langflow/initial_setup/starter_projects/Vector Store RAG.json
Replaced the brief README with a comprehensive explanation of Retrieval Augmented Generation, detailed usage instructions for both data loading and retrieval flows, credential setup, and guidance for experimentation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Suggested labels

documentation, size:L, lgtm

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch lfoss-1556-2

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 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.

@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jul 29, 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

🧹 Nitpick comments (5)
src/backend/base/langflow/initial_setup/starter_projects/Travel Planning Agents.json (1)

811-813: Fix duplicate list numbering in Quick-start note

The updated README text looks good overall, but the ordered list under “Quickstart” has two items numbered 2..
Cleaning this up will avoid confusing readers and keeps the docs polished.

-## Quickstart
-1. Add your **OpenAI API Key** to each Agent.
-2. Add your **Search API** key to the Search API component.
-2. Run the flow in the **Playground**.
+## Quickstart
+1. Add your **OpenAI API Key** to each Agent.
+2. Add your **Search API** key to the Search API component.
+3. Run the flow in the **Playground**.
src/backend/base/langflow/initial_setup/starter_projects/Financial Report Parser.json (1)

783-783: Correct description to match schema fields & fix grammar

The note claims the flow extracts “gross profit, EBITDA, net income, and operating expenses”, yet the Structured Output schema & parser pattern only include GROSS_PROFIT, EBITDA, and NET_INCOME.
It also contains a grammatical error: “into a messages”.

Update the copy or extend the schema/pattern to avoid confusing users.

-…retrieves the gross profit, EBITDA, net income, and operating expenses information from the financial report. Then, the **Structured Output** component formats extracted data into a structured format for better readability and further processing. Finally, the **Parser** component converts extracted data into a messages to be returned to the user.
+…retrieves the Gross Profit, EBITDA, and Net Income information from the financial report. The **Structured Output** component then formats the extracted data into a structured format for better readability and further processing. Finally, the **Parser** component converts the structured data into messages to be returned to the user.
src/backend/base/langflow/initial_setup/starter_projects/Basic Prompting.json (1)

519-519: Align wording with Langflow terminology conventions

Per the docs conventions, always capitalize the key Langflow concepts:

  • “Component” → Language Model Component
  • “Flow” → Flow

Consider updating the note to preserve consistency:

-1. Add your **OpenAI API Key** to the **Language Model** component, or select a different provider and model.
+1. Add your **OPENAI API Key** to the **Language Model** Component, or select a different provider and model.

-2. Open the **Playground** to start the chat and run the flow.
+2. Open the **Playground** to start the chat and run the Flow.

(Feel free to adjust further occurrences of “component” / “flow” where you are referring to the Langflow primitives.)

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

739-742: Ensure style-guide capitalization for “Component” and “Flow”.

The docs guidelines for docs/**/*.{md,mdx} mandate capitalizing the terms “Component” and “Flow”.
In this updated note markdown, component/components appear in lower case several times (e.g. “Message History component”, “Language Model component”, section heading About the Message History component). Consider changing these to “Component/Components” for consistency with the rest of the docs.

Example patch:

-This flow extends the **Basic Prompting** template by adding a **Message History** component
+This Flow extends the **Basic Prompting** template by adding a **Message History** Component
@@
-1. In the **Language Model** component, add your OpenAI API key, or select a different provider and model.
+1. In the **Language Model** Component, add your OpenAI API key, or select a different provider and model.
@@
-## About the Message History component
+## About the Message History Component
@@
-The **Language Model** and **Agent** components have built-in chat memory
+The **Language Model** and **Agent** Components have built-in chat memory

Purely stylistic, but aligning with the repo’s preferred terminology keeps the docs polished.

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

1021-1021: Fix minor grammar & adhere to capitalization guideline

Docs rule: always capitalize “Flow”; also there’s an extra “the” in “Only the run…”.

-Only the run the **Load Data** flow when you need to populate your vector database with baseline content, such as product data.
+Only run the **Load Data** Flow when you need to populate your vector database with baseline content, such as product data.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 575cb7f and 18a6872.

📒 Files selected for processing (6)
  • src/backend/base/langflow/initial_setup/starter_projects/Basic Prompting.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Financial Report Parser.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Memory Chatbot.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Sequential Tasks Agents.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Travel Planning Agents.json (1 hunks)
  • src/backend/base/langflow/initial_setup/starter_projects/Vector Store RAG.json (1 hunks)
🧰 Additional context used
🧠 Learnings (7)
📓 Common learnings
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
src/backend/base/langflow/initial_setup/starter_projects/Travel Planning Agents.json (1)

Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored

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

Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored

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

Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored

src/backend/base/langflow/initial_setup/starter_projects/Basic Prompting.json (1)

Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored

src/backend/base/langflow/initial_setup/starter_projects/Financial Report Parser.json (2)

Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored

Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.

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

Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-07-18T18:25:54.486Z
Learning: Starter project files auto-format after langflow run; these formatting changes can be committed or ignored

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: test-starter-projects
🔇 Additional comments (1)
src/backend/base/langflow/initial_setup/starter_projects/Sequential Tasks Agents.json (1)

2071-2073: Well-structured quick-start note – LGTM

The new numbered checklist and contextual guidance make the template a lot clearer for first-time users. No functional concerns spotted.

@SonicDMG SonicDMG temporarily deployed to lfoss-1556-2 - langflow-manual-install PR #9230 July 30, 2025 17:11 — with Render Destroyed
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Jul 30, 2025
Copy link
Copy Markdown
Collaborator

@edwinjosechittilappilly edwinjosechittilappilly left a comment

Choose a reason for hiding this comment

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

LGTM

@github-actions github-actions Bot added the lgtm This PR has been approved by a maintainer label Aug 1, 2025
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Aug 1, 2025
@github-actions github-actions Bot added documentation Improvements or additions to documentation and removed documentation Improvements or additions to documentation labels Aug 1, 2025
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Aug 1, 2025

@codecov
Copy link
Copy Markdown

codecov Bot commented Aug 1, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 32.61%. Comparing base (aa41577) to head (44e62bb).
⚠️ Report is 3 commits behind head on main.

❌ Your project status has failed because the head coverage (1.21%) is below the target coverage (10.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #9230   +/-   ##
=======================================
  Coverage   32.61%   32.61%           
=======================================
  Files        1193     1193           
  Lines       56007    56001    -6     
  Branches     5278     5278           
=======================================
  Hits        18266    18266           
+ Misses      37691    37685    -6     
  Partials       50       50           
Flag Coverage Δ
backend 55.52% <ø> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 3 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@edwinjosechittilappilly edwinjosechittilappilly added this pull request to the merge queue Aug 1, 2025
Merged via the queue into main with commit 3369e28 Aug 1, 2025
70 of 71 checks passed
@edwinjosechittilappilly edwinjosechittilappilly deleted the lfoss-1556-2 branch August 1, 2025 13:23
2getsandesh pushed a commit to 2getsandesh/langflow-IBM that referenced this pull request Aug 6, 2025
* update travel agent template description

* update vector store rag description

* update sequential task agent description

* update chat memory template description

* update financial report parser description

* update basic prompting template description

---------

Co-authored-by: Edwin Jose <edwin.jose@datastax.com>
lucaseduoli pushed a commit that referenced this pull request Aug 12, 2025
* update travel agent template description

* update vector store rag description

* update sequential task agent description

* update chat memory template description

* update financial report parser description

* update basic prompting template description

---------

Co-authored-by: Edwin Jose <edwin.jose@datastax.com>
lucaseduoli pushed a commit that referenced this pull request Aug 22, 2025
* update travel agent template description

* update vector store rag description

* update sequential task agent description

* update chat memory template description

* update financial report parser description

* update basic prompting template description

---------

Co-authored-by: Edwin Jose <edwin.jose@datastax.com>
lucaseduoli pushed a commit that referenced this pull request Aug 25, 2025
* update travel agent template description

* update vector store rag description

* update sequential task agent description

* update chat memory template description

* update financial report parser description

* update basic prompting template description

---------

Co-authored-by: Edwin Jose <edwin.jose@datastax.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation lgtm This PR has been approved by a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants