docs: link components to docs pages#8766
Conversation
github-actions
Bot
added
documentation
|
Build successful! ✅ |
github-actions
Bot
added
documentation
dosubot
Bot
added
size:XL
github-actions
Bot
added
documentation
dosubot
Bot
added
size:XXL
github-actions
Bot
added
documentation
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 15
🔭 Outside diff range comments (6)
src/backend/base/langflow/components/logic/loop.py (1)
60-63: Fence-post error in loop termination
evaluate_stop_loopshould stop whencurrent_indexequals the data length, otherwise an extra empty item is emitted.-return current_index > data_length +return current_index >= data_lengthdocs/docs/Concepts/concepts-flows.md (1)
1-4: Add the requireddescriptionto the front-matter blockAll docs pages must include at least the
titleanddescriptionfields in the front-matter.
Without thedescription, the page fails the documentation guidelines and may break the Docusaurus build.--- title: Flows slug: /concepts-flows +description: Learn how to import and export Flow JSON files in Langflow. ---docs/docs/Templates/simple-agent.md (1)
1-4: Front-matter missingdescriptionAdd a concise description so the page meets the docs front-matter requirements.
--- title: Simple agent slug: /simple-agent +description: Build and run a Simple Agent Flow that uses tools like Calculator and URL fetch. ---docs/docs/Components/components-tools.md (1)
1-4: Add missingdescriptionto front-matter--- title: Tools slug: /components-tools +description: Overview of legacy Tools components and their new locations in Langflow 1.5. ---docs/docs/Concepts/concepts-playground.md (1)
1-4: Missingdescriptionin front-matter--- title: Playground slug: /concepts-playground +description: Interact with your Flows in real-time using the Langflow Playground. ---docs/docs/Components/components-processing.md (1)
1-4: Front-matter missingdescription
Every docs file must provide adescription:in the front-matter.--- title: Processing +description: Detailed guide to Langflow processing Components such as Batch Run, Data operations, LLM Router, etc. slug: /components-processing ---
🧹 Nitpick comments (45)
docs/docs/API-Reference/api-monitor.md (1)
673-673: Ensure file ends with a newline.The last changed line is the closing
</Tabs>tag with no blank line after it. Docusaurus’ MDX parser is forgiving, but we generally keep a trailing newline to avoid diffs showing up in future edits.-</Tabs> +</Tabs> +docs/docs/API-Reference/api-build.md (1)
161-165: List looks good, but keep items in logical order.Placing “Delete Vertex builds” last is fine; just double-check that every bullet remains alphabetically or logically grouped to avoid churn in future diffs.
docs/docs/Components/components-io.md (1)
264-265: Good confirmation sentence, minor comma splice.Consider adding a comma after “command” for smoother reading.
-The value for `should_store_message` is `false`. +The value for `should_store_message` is `false`.(Only punctuation style; feel free to ignore.)
docs/docs/Integrations/Notion/notion-agent-meeting-notes.md (1)
6-8: Use lowercase boolean foraria-hidden; keep doc JSX tidy
aria-hiddenexpects the lowercase boolean"true". Using"True"may trip some accessibility linters.-<Icon name="Play" aria-hidden="True" /> **Run component** +<Icon name="Play" aria-hidden="true" /> **Run component**src/backend/base/langflow/components/agents/agent.py (1)
36-36: Use HTTPS and keep URL format consistent across components.All other components use
https://docs.langflow.org/...; this one uses plain HTTP and a slightly different path. Recommend switching to HTTPS and, if applicable, mirroring thecomponents-agents#agentanchor style for uniformity.- documentation: str = "http://docs.langflow.org/agents" + documentation: str = "https://docs.langflow.org/components-agents#agent"docs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.md (1)
49-50: HTML accessibility nitpick
aria-hiddenaccepts lowercase boolean strings. Usearia-hidden="true"instead of"True"to avoid validation warnings.-<Icon name="Play" aria-hidden="True" /> **Run component** +<Icon name="Play" aria-hidden="true" /> **Run component**src/backend/base/langflow/components/models/language_model.py (1)
19-22: Documentation URL added – minor naming suggestionConsider making the anchor more specific (
#language-model) to future-proof against heading changes on the page.Otherwise, looks fine.
src/backend/base/langflow/components/processing/data_operations.py (1)
33-37: Add centralised helper for documentation URLsRepeated literal URLs across many component classes will become a maintenance burden (e.g. mass rename if the docs site structure changes).
Consider introducing a tiny helper (or even a constant map) underlangflow.utils.documentationand assign:from langflow.utils.documentation import DOCS documentation: str = DOCS["data-operations"]This keeps component files tidy and avoids future hunting for hard-coded strings.
src/backend/base/langflow/components/processing/dataframe_operations.py (1)
15-19: Same centralisation concern for doc linksSee previous comment ― hard-coding URLs makes future re-organisation painful.
A shared constant (or enum) avoids drift.docs/docs/Integrations/integrations-assemblyai.md (1)
140-142:aria-hiddenvalue should be lowercaseHTML attributes are case-sensitive for boolean strings. Use
"true"instead of"True"to satisfy accessibility checkers and MDX/JSX linting.-<Icon name="Play" aria-hidden="True" /> +<Icon name="Play" aria-hidden="true" />docs/docs/Templates/basic-prompting.md (1)
40-48: Hard tabs trigger markdown-lint (MD010)Lines 42–47 contain hard tab characters. Replace with 4 spaces for consistency and to satisfy
markdownlint.- Optionally, create a [global variable](/configuration-global-variables) for the **OpenAI API key**. - 1. In the **OpenAI API Key** field, click <Icon name="Globe" aria-hidden="True" /> **Globe**, and then click **Add New Variable**. - 2. In the **Variable Name** field, enter `openai_api_key`. - 3. In the **Value** field, paste your OpenAI API Key (`sk-...`). - 4. Click **Save Variable**. + Optionally, create a [global variable](/configuration-global-variables) for the **OpenAI API key**. + 1. In the **OpenAI API Key** field, click <Icon name="Globe" aria-hidden="true" /> **Globe**, and then click **Add New Variable**. + 2. In the **Variable Name** field, enter `openai_api_key`. + 3. In the **Value** field, paste your OpenAI API key (`sk-...`). + 4. Click **Save Variable**.docs/docs/Templates/document-qa.md (3)
24-26: Replace legacy “OpenAI component” referenceThe flow no longer exposes an OpenAI-specific component. Update the sentence to keep terminology consistent with the new unified Language model component.
-This gives the **OpenAI** component context it would not otherwise have access to. +This gives the **Language model** component context it would not otherwise have access to.
30-30: Remove duplicated word “model”-1. Add your **OpenAI API key** to the **Language model** model component. +1. Add your **OpenAI API key** to the **Language model** component.
31-36: Convert hard tabs to spaces to satisfy markdown-lintSeveral nested list items are indented with literal tabs. Replace them with two-space indents to eliminate
MD010 no-hard-tabsand keep rendering predictable.docs/docs/Templates/vector-store-rag.md (3)
25-27: Fix hard-tab indentation in prerequisites sub-listReplace the tab characters before the two bullet points with two spaces each to satisfy
MD007 ul-indentandMD010 no-hard-tabs.
Example:- - An Astra DB application token scoped … - - A collection created … + - An Astra DB application token scoped … + - A collection created …
52-53: Drop provider-specific wording in component descriptionThe unified component is already called Language model; mentioning “OpenAI LLM” re-introduces a provider detail that the doc just abstracted away.
-**Language model** generates the response using the prompt and the OpenAI LLM. +**Language model** generates the response using the prompt.
57-62: Replace tabs with spaces inside the global-variable stepsLines 59-62 are indented with tabs, triggering multiple markdown-lint complaints. Convert to spaces for consistency and cleaner diffs.
docs/docs/Templates/blog-writer.md (2)
27-27: Consistent casing for component nameUse “Language model”, not “Language Model”, to match the rest of the docs.
-This flow creates a blog article generator with **Prompt**, **Language Model**, and **Chat Output** components, +This flow creates a blog article generator with **Prompt**, **Language model**, and **Chat Output** components,
51-51: Remove duplicate word “model”-1. Add your **OpenAI API key** to the **Language model** model component. +1. Add your **OpenAI API key** to the **Language model** component.docs/docs/Concepts/mcp-server.md (3)
40-42: Remove duplicated word “the”-…template that you can use to connect MCP clients to the the project's MCP server. +…template that you can use to connect MCP clients to the project's MCP server.
54-55: Fix typo in guidance-Enter a name thats makes it clear what the flow does. +Enter a name that makes it clear what the flow does.
360-367: Grammar & hyphenation in auto-install section
- Hyphenate compound adjective “auto-install”.
- Correct conditional wording.
-In the **MCP server** tab, an **Auto install** option … -… -In this is not the case, configure the client with the code in the **JSON** tab. +In the **MCP Server** tab, an **Auto-install** option … +… +If this is not the case, configure the client with the code in the **JSON** tab.docs/docs/Develop/memory.md (1)
51-51: Correct typo in alt text- +docs/docs/Templates/financial-report-parser.md (2)
8-8: Capitalize Component Names Consistently
Structured outputshould follow the project-wide terminology rule and be capitalized as Structured Output.-Build a **Financial Report Parser** flow with the [Structured output](/components-processing#structured-output) and ... +Build a **Financial Report Parser** Flow with the [Structured Output](/components-processing#structured-output) and ...
26-26: Capitalize “Flow” in the HeadingThe term Flow is a first-class Langflow concept and should always be capitalized.
-## Run the financial report parser flow +## Run the Financial Report Parser Flowdocs/docs/Components/components-logic.md (1)
236-244: Convert emphasised text to proper sub-headings
**Inputs**and**Outputs**are rendered as bold text, but markdown-lint flags this (MD036). Use fourth-level headings instead to improve structure and navigation.-**Inputs** +#### Inputs ... -**Outputs** +#### Outputsdocs/docs/Templates/memory-chatbot.md (2)
31-31: Component name should be Title-caseUse Language Model (title-case) to match the sidebar label and maintain consistency.
-The **Prompt** instructs the **Language model** component how to respond to input. +The **Prompt** instructs the **Language Model** component how to respond to input.
60-63: Clarify UI instruction and fix casing
- Casing: “Message logs” in the UI is sentence-case ⇒ Message Logs
- The nested list currently confuses users; split the action into two clear steps.
-3. To view the **Message Logs** pane, in the **Playground** pane, click <Icon name="Ellipsis" aria-hidden="true"/> **Options**, and then click **Message logs**. -The **Message Logs** pane displays all previous messages. +3. In the **Playground** pane, click <Icon name="Ellipsis" aria-hidden="true" /> **Options**. +4. Click **Message Logs**. + The pane displays all previous messages.docs/docs/Support/release-notes.md (1)
41-45: Fix list indentation (MD007) and keep bullets at two-space levelIndent the nested unordered list by two spaces only.
- * To replace legacy search components like Bing Search and Google, use the [Web search](/components-data#web-search) component. - * To replace legacy news aggregation components, use the [News search](/components-data#news-search) component. + * To replace legacy search components like Bing Search and Google, use the [Web search](/components-data#web-search) component. + * To replace legacy news aggregation components, use the [News search](/components-data#news-search) component.docs/docs/Components/components-memories.md (1)
18-19: Remove comma before “because”-They are distinct from vector store components, because they are built specifically ... +They are distinct from vector store components because they are built specifically ...docs/docs/Templates/simple-agent.md (1)
6-14: Use capital “Flow” when referring to the concept-Build a **Simple Agent** flow for an agentic application using the [Agent](/components-agents) component. +Build a **Simple Agent** Flow for an agentic application using the [Agent](/components-agents) Component. ... -In this flow, the **Agent** reasons using a connected [Language model](/components-models) component. +In this Flow, the **Agent** reasons using a connected [Language Model](/components-models) Component.docs/docs/Components/components-tools.md (1)
12-16: Correct component names and typoMaintain consistent capitalization and fix “re-named”.
-* The [calculator](/components-helpers#calculator) component is available in **Helpers**. -* The [Astra DB JSON](/components-tools#astra-db-tool) and [Astra DB CQL](#astra-db-cql-tool) tools are available in the **DataStax** bundle. -* The Python REPL tool is available in **Processing** and re-named the [Python Interpreter](/components-processing#python-interpreter) component. +* The [Calculator](/components-helpers#calculator) Component is available in **Helpers**. +* The [Astra DB JSON](/components-tools#astra-db-tool) and [Astra DB CQL](#astra-db-cql-tool) Tools are available in the **DataStax** bundle. +* The Python REPL tool is now the [Python Interpreter](/components-processing#python-interpreter) Component in **Processing**.docs/docs/Concepts/concepts-publish.md (1)
37-43: Remove duplicated word and clarify sentence-**MCP server** exposes your flows as [tools](https://modelcontextprotocol.io/docs/concepts/tools) that [MCP clients](https://modelcontextprotocol.io/clients) can use use to take actions. +**MCP server** exposes your Flows as [Tools](https://modelcontextprotocol.io/docs/concepts/tools) that [MCP clients](https://modelcontextprotocol.io/clients) can use to take actions.docs/docs/Concepts/concepts-playground.md (1)
10-18: Header and terminology capitalization-As long as you have a [Chat Input](/components-io) component in your flow, you can run and chat with your flow by clicking the **Playground** button. +As long as your Flow contains a [Chat Input](/components-io) Component, you can run and chat with the Flow by clicking the **Playground** button. ... -## Run a flow in the playground +## Run a Flow in the Playground ... -To run a flow in the **Playground**, click **Playground**. +To run a Flow in the **Playground**, click **Playground**.docs/docs/Components/components-bundles.md (1)
304-305: Redundant closing tagTwo consecutive
</details>close tags render an empty block.-</details> -</details> +</details>docs/docs/Components/components-embedding-models.md (2)
29-33: Typo: “Language Moodel”-Use a **Language Moodel** component … +Use a **Language Model** component …
48-50: Grammar – duplicated article-To query the your vector store, include … +To query your vector store, include …docs/docs/Concepts/concepts-overview.md (1)
40-41: Unclear anchor list – add commas for readabilityThe sentence enumerating the four regions reads as a run-on. Consider splitting or adding commas to aid scanning.
docs/docs/Components/components-helpers.md (2)
70-74: Spelling: “Redit” → “Redis”-This example uses **Redit Chat Memory**. +This example uses **Redis Chat Memory**.
52-55: Wordiness – replace “Prior to”Consistency with style-guide (“short, direct sentences”):
-Prior to Langflow 1.5, this component was two separate components … +Before Langflow 1.5, this functionality was split across two components …docs/docs/Components/components-models.md (2)
29-31: Typo: “Language Moodel”-Use a **Language Moodel** component … +Use a **Language Model** component …
78-79: Style – “outside of”Redundant “of”:
-The response from the Anthropic model is less verbose, and lists its sources outside of the informative paragraph. +The Anthropic response is less verbose and lists its sources outside the informative paragraph.docs/docs/Concepts/concepts-components.md (1)
242-246: Missing comma after introductory clause
Language-Tool flagged:
Legacy components are available for use but are no longer supported.→ needs a comma before “but”.-Legacy components are available for use but are no longer supported. +Legacy components are available for use, but are no longer supported.docs/docs/Components/components-processing.md (2)
74-101: Code block indentation breaks fenced-code detection
Indenting the entirecurlexample by four spaces makes it render as plain text instead of a fenced block. Remove the indentation or add an explicit language fence inside the list item.- ```bash +```bash curl -X POST … … - ``` +```
360-371: Minor repetition & wording
Sentence “To use this component in a flow,in the Global Imports field, add …” contains a missing space after the comma and repeats “to use this component” several times in adjacent sentences. Tighten wording for readability.
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (45)
docs/static/img/agent-component.pngis excluded by!**/*.pngdocs/static/img/api-pane.pngis excluded by!**/*.pngdocs/static/img/astra_db_chat_memory_rounded.pngis excluded by!**/*.pngdocs/static/img/chat-input-controls-pane.pngis excluded by!**/*.pngdocs/static/img/component-api-request-chat-output.pngis excluded by!**/*.pngdocs/static/img/component-batch-run.pngis excluded by!**/*.pngdocs/static/img/component-chat-io.pngis excluded by!**/*.pngdocs/static/img/component-chroma-db.pngis excluded by!**/*.pngdocs/static/img/component-conditional-router.pngis excluded by!**/*.pngdocs/static/img/component-dataframe-operations.pngis excluded by!**/*.pngdocs/static/img/component-embedding-models-add-chat.pngis excluded by!**/*.pngdocs/static/img/component-embedding-models.pngis excluded by!**/*.pngdocs/static/img/component-lambda-filter.pngis excluded by!**/*.pngdocs/static/img/component-language-model.pngis excluded by!**/*.pngdocs/static/img/component-llm-router.pngis excluded by!**/*.pngdocs/static/img/component-loop-csv.pngis excluded by!**/*.pngdocs/static/img/component-message-history-external-memory.pngis excluded by!**/*.pngdocs/static/img/component-message-history-message-store.pngis excluded by!**/*.pngdocs/static/img/component-parser.pngis excluded by!**/*.pngdocs/static/img/component-python-interpreter.pngis excluded by!**/*.pngdocs/static/img/component-run-flow.pngis excluded by!**/*.pngdocs/static/img/component-split-text.pngis excluded by!**/*.pngdocs/static/img/component-sql-database.pngis excluded by!**/*.pngdocs/static/img/component-structured-output.pngis excluded by!**/*.pngdocs/static/img/component-type-convert-and-web-search.pngis excluded by!**/*.pngdocs/static/img/component-url-regex.pngis excluded by!**/*.pngdocs/static/img/component-url.pngis excluded by!**/*.pngdocs/static/img/connect-component.pngis excluded by!**/*.pngdocs/static/img/connect-data-components-to-agent.pngis excluded by!**/*.pngdocs/static/img/flows/import.gifis excluded by!**/*.gifdocs/static/img/logs.pngis excluded by!**/*.pngdocs/static/img/loop-text-summarizer.pngis excluded by!**/*.pngdocs/static/img/messages-logs.pngis excluded by!**/*.pngdocs/static/img/playground-with-agent.pngis excluded by!**/*.pngdocs/static/img/playground.pngis excluded by!**/*.pngdocs/static/img/prompt-component-with-multiple-inputs.pngis excluded by!**/*.pngdocs/static/img/prompt-component.pngis excluded by!**/*.pngdocs/static/img/starter-flow-basic-prompting.pngis excluded by!**/*.pngdocs/static/img/starter-flow-blog-writer.pngis excluded by!**/*.pngdocs/static/img/starter-flow-document-qa.pngis excluded by!**/*.pngdocs/static/img/starter-flow-financial-report-parser.pngis excluded by!**/*.pngdocs/static/img/starter-flow-memory-chatbot.pngis excluded by!**/*.pngdocs/static/img/starter-flow-vector-rag.pngis excluded by!**/*.pngdocs/static/img/workspace-basic-prompting.pngis excluded by!**/*.pngdocs/static/img/workspace.pngis excluded by!**/*.png
📒 Files selected for processing (67)
docs/docs/API-Reference/api-build.md(1 hunks)docs/docs/API-Reference/api-monitor.md(1 hunks)docs/docs/Components/components-bundles.md(2 hunks)docs/docs/Components/components-embedding-models.md(1 hunks)docs/docs/Components/components-helpers.md(6 hunks)docs/docs/Components/components-io.md(2 hunks)docs/docs/Components/components-logic.md(1 hunks)docs/docs/Components/components-memories.md(1 hunks)docs/docs/Components/components-models.md(2 hunks)docs/docs/Components/components-processing.md(14 hunks)docs/docs/Components/components-prompts.md(2 hunks)docs/docs/Components/components-tools.md(14 hunks)docs/docs/Concepts/concepts-components.md(2 hunks)docs/docs/Concepts/concepts-flows.md(1 hunks)docs/docs/Concepts/concepts-objects.md(1 hunks)docs/docs/Concepts/concepts-overview.md(4 hunks)docs/docs/Concepts/concepts-playground.md(2 hunks)docs/docs/Concepts/concepts-publish.md(1 hunks)docs/docs/Concepts/mcp-server.md(2 hunks)docs/docs/Develop/memory.md(1 hunks)docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md(1 hunks)docs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.md(2 hunks)docs/docs/Integrations/Notion/notion-agent-meeting-notes.md(2 hunks)docs/docs/Integrations/integrations-assemblyai.md(2 hunks)docs/docs/Support/release-notes.md(1 hunks)docs/docs/Templates/basic-prompting.md(1 hunks)docs/docs/Templates/blog-writer.md(3 hunks)docs/docs/Templates/document-qa.md(2 hunks)docs/docs/Templates/financial-report-parser.md(3 hunks)docs/docs/Templates/memory-chatbot.md(5 hunks)docs/docs/Templates/simple-agent.md(2 hunks)docs/docs/Templates/vector-store-rag.md(2 hunks)docs/sidebars.js(1 hunks)src/backend/base/langflow/components/agents/agent.py(1 hunks)src/backend/base/langflow/components/agents/mcp_component.py(1 hunks)src/backend/base/langflow/components/data/api_request.py(1 hunks)src/backend/base/langflow/components/data/directory.py(1 hunks)src/backend/base/langflow/components/data/file.py(1 hunks)src/backend/base/langflow/components/data/news_search.py(1 hunks)src/backend/base/langflow/components/data/rss.py(1 hunks)src/backend/base/langflow/components/data/sql_executor.py(1 hunks)src/backend/base/langflow/components/data/url.py(2 hunks)src/backend/base/langflow/components/data/web_search.py(1 hunks)src/backend/base/langflow/components/data/webhook.py(1 hunks)src/backend/base/langflow/components/helpers/calculator_core.py(1 hunks)src/backend/base/langflow/components/helpers/current_date.py(1 hunks)src/backend/base/langflow/components/helpers/memory.py(1 hunks)src/backend/base/langflow/components/input_output/chat.py(1 hunks)src/backend/base/langflow/components/input_output/chat_output.py(1 hunks)src/backend/base/langflow/components/input_output/text.py(1 hunks)src/backend/base/langflow/components/input_output/text_output.py(1 hunks)src/backend/base/langflow/components/logic/conditional_router.py(1 hunks)src/backend/base/langflow/components/logic/loop.py(1 hunks)src/backend/base/langflow/components/logic/run_flow.py(1 hunks)src/backend/base/langflow/components/models/embedding_model.py(1 hunks)src/backend/base/langflow/components/models/language_model.py(1 hunks)src/backend/base/langflow/components/processing/batch_run.py(1 hunks)src/backend/base/langflow/components/processing/converter.py(1 hunks)src/backend/base/langflow/components/processing/data_operations.py(1 hunks)src/backend/base/langflow/components/processing/dataframe_operations.py(1 hunks)src/backend/base/langflow/components/processing/lambda_filter.py(1 hunks)src/backend/base/langflow/components/processing/llm_router.py(1 hunks)src/backend/base/langflow/components/processing/parser.py(1 hunks)src/backend/base/langflow/components/processing/prompt.py(1 hunks)src/backend/base/langflow/components/processing/save_file.py(1 hunks)src/backend/base/langflow/components/processing/split_text.py(1 hunks)src/backend/base/langflow/components/processing/structured_output.py(1 hunks)
🧰 Additional context used
📓 Path-based instructions (6)
`src/backend/base/langflow/components/**/*.py`: Add new backend components to th...
src/backend/base/langflow/components/**/*.py: Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Implement async component methods using async def and await for asynchronous operations
Use asyncio.create_task for background work in async components and ensure proper cleanup on cancellation
Use asyncio.Queue for non-blocking queue operations in async components and handle timeouts appropriately
📄 Source: CodeRabbit Inference Engine (.cursor/rules/backend_development.mdc)
List of files the instruction was applied to:
src/backend/base/langflow/components/data/sql_executor.pysrc/backend/base/langflow/components/agents/agent.pysrc/backend/base/langflow/components/data/rss.pysrc/backend/base/langflow/components/helpers/calculator_core.pysrc/backend/base/langflow/components/logic/conditional_router.pysrc/backend/base/langflow/components/processing/prompt.pysrc/backend/base/langflow/components/models/language_model.pysrc/backend/base/langflow/components/input_output/text_output.pysrc/backend/base/langflow/components/input_output/chat.pysrc/backend/base/langflow/components/data/api_request.pysrc/backend/base/langflow/components/processing/lambda_filter.pysrc/backend/base/langflow/components/logic/loop.pysrc/backend/base/langflow/components/data/directory.pysrc/backend/base/langflow/components/logic/run_flow.pysrc/backend/base/langflow/components/input_output/text.pysrc/backend/base/langflow/components/processing/parser.pysrc/backend/base/langflow/components/models/embedding_model.pysrc/backend/base/langflow/components/data/webhook.pysrc/backend/base/langflow/components/helpers/current_date.pysrc/backend/base/langflow/components/data/url.pysrc/backend/base/langflow/components/processing/converter.pysrc/backend/base/langflow/components/processing/split_text.pysrc/backend/base/langflow/components/processing/structured_output.pysrc/backend/base/langflow/components/helpers/memory.pysrc/backend/base/langflow/components/processing/batch_run.pysrc/backend/base/langflow/components/processing/save_file.pysrc/backend/base/langflow/components/data/web_search.pysrc/backend/base/langflow/components/data/file.pysrc/backend/base/langflow/components/processing/data_operations.pysrc/backend/base/langflow/components/processing/dataframe_operations.pysrc/backend/base/langflow/components/processing/llm_router.pysrc/backend/base/langflow/components/data/news_search.pysrc/backend/base/langflow/components/input_output/chat_output.pysrc/backend/base/langflow/components/agents/mcp_component.py
`src/backend/**/*.py`: Run make format_backend to format Python code early and often Run make lint to check for linting issues in backend Python code
src/backend/**/*.py: Run make format_backend to format Python code early and often
Run make lint to check for linting issues in backend Python code
📄 Source: CodeRabbit Inference Engine (.cursor/rules/backend_development.mdc)
List of files the instruction was applied to:
src/backend/base/langflow/components/data/sql_executor.pysrc/backend/base/langflow/components/agents/agent.pysrc/backend/base/langflow/components/data/rss.pysrc/backend/base/langflow/components/helpers/calculator_core.pysrc/backend/base/langflow/components/logic/conditional_router.pysrc/backend/base/langflow/components/processing/prompt.pysrc/backend/base/langflow/components/models/language_model.pysrc/backend/base/langflow/components/input_output/text_output.pysrc/backend/base/langflow/components/input_output/chat.pysrc/backend/base/langflow/components/data/api_request.pysrc/backend/base/langflow/components/processing/lambda_filter.pysrc/backend/base/langflow/components/logic/loop.pysrc/backend/base/langflow/components/data/directory.pysrc/backend/base/langflow/components/logic/run_flow.pysrc/backend/base/langflow/components/input_output/text.pysrc/backend/base/langflow/components/processing/parser.pysrc/backend/base/langflow/components/models/embedding_model.pysrc/backend/base/langflow/components/data/webhook.pysrc/backend/base/langflow/components/helpers/current_date.pysrc/backend/base/langflow/components/data/url.pysrc/backend/base/langflow/components/processing/converter.pysrc/backend/base/langflow/components/processing/split_text.pysrc/backend/base/langflow/components/processing/structured_output.pysrc/backend/base/langflow/components/helpers/memory.pysrc/backend/base/langflow/components/processing/batch_run.pysrc/backend/base/langflow/components/processing/save_file.pysrc/backend/base/langflow/components/data/web_search.pysrc/backend/base/langflow/components/data/file.pysrc/backend/base/langflow/components/processing/data_operations.pysrc/backend/base/langflow/components/processing/dataframe_operations.pysrc/backend/base/langflow/components/processing/llm_router.pysrc/backend/base/langflow/components/data/news_search.pysrc/backend/base/langflow/components/input_output/chat_output.pysrc/backend/base/langflow/components/agents/mcp_component.py
`src/backend/**/components/**/*.py`: In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
src/backend/**/components/**/*.py: In your Python component class, set theiconattribute to a string matching the frontend icon mapping exactly (case-sensitive).
📄 Source: CodeRabbit Inference Engine (.cursor/rules/icons.mdc)
List of files the instruction was applied to:
src/backend/base/langflow/components/data/sql_executor.pysrc/backend/base/langflow/components/agents/agent.pysrc/backend/base/langflow/components/data/rss.pysrc/backend/base/langflow/components/helpers/calculator_core.pysrc/backend/base/langflow/components/logic/conditional_router.pysrc/backend/base/langflow/components/processing/prompt.pysrc/backend/base/langflow/components/models/language_model.pysrc/backend/base/langflow/components/input_output/text_output.pysrc/backend/base/langflow/components/input_output/chat.pysrc/backend/base/langflow/components/data/api_request.pysrc/backend/base/langflow/components/processing/lambda_filter.pysrc/backend/base/langflow/components/logic/loop.pysrc/backend/base/langflow/components/data/directory.pysrc/backend/base/langflow/components/logic/run_flow.pysrc/backend/base/langflow/components/input_output/text.pysrc/backend/base/langflow/components/processing/parser.pysrc/backend/base/langflow/components/models/embedding_model.pysrc/backend/base/langflow/components/data/webhook.pysrc/backend/base/langflow/components/helpers/current_date.pysrc/backend/base/langflow/components/data/url.pysrc/backend/base/langflow/components/processing/converter.pysrc/backend/base/langflow/components/processing/split_text.pysrc/backend/base/langflow/components/processing/structured_output.pysrc/backend/base/langflow/components/helpers/memory.pysrc/backend/base/langflow/components/processing/batch_run.pysrc/backend/base/langflow/components/processing/save_file.pysrc/backend/base/langflow/components/data/web_search.pysrc/backend/base/langflow/components/data/file.pysrc/backend/base/langflow/components/processing/data_operations.pysrc/backend/base/langflow/components/processing/dataframe_operations.pysrc/backend/base/langflow/components/processing/llm_router.pysrc/backend/base/langflow/components/data/news_search.pysrc/backend/base/langflow/components/input_output/chat_output.pysrc/backend/base/langflow/components/agents/mcp_component.py
`docs/docs/**/*.{md,mdx}`: All documentation content must be placed within the '...
docs/docs/**/*.{md,mdx}: All documentation content must be placed within the 'docs/' directory, organized into subdirectories such as 'getting-started', 'components', 'integrations', 'administration', 'contributing', and 'api-reference'.
All documentation markdown files must start with a frontmatter block containing at least 'title' and 'description' fields.
Use admonitions (:::tip, :::warning, :::danger) in markdown files to highlight important information, warnings, or critical issues.
Reference images in documentation using the '/img/' path and provide descriptive alt text in markdown.
Use code blocks with language identifiers and optional titles for code examples in markdown documentation.
Documentation content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
📄 Source: CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
List of files the instruction was applied to:
docs/docs/API-Reference/api-monitor.mddocs/docs/Components/components-prompts.mddocs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.mddocs/docs/Integrations/Notion/notion-agent-meeting-notes.mddocs/docs/Components/components-io.mddocs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.mddocs/docs/API-Reference/api-build.mddocs/docs/Integrations/integrations-assemblyai.mddocs/docs/Templates/blog-writer.mddocs/docs/Templates/basic-prompting.mddocs/docs/Templates/document-qa.mddocs/docs/Develop/memory.mddocs/docs/Templates/memory-chatbot.mddocs/docs/Concepts/mcp-server.mddocs/docs/Templates/financial-report-parser.mddocs/docs/Templates/vector-store-rag.mddocs/docs/Concepts/concepts-objects.mddocs/docs/Components/components-memories.mddocs/docs/Components/components-logic.mddocs/docs/Templates/simple-agent.mddocs/docs/Support/release-notes.mddocs/docs/Concepts/concepts-flows.mddocs/docs/Concepts/concepts-publish.mddocs/docs/Concepts/concepts-playground.mddocs/docs/Components/components-tools.mddocs/docs/Concepts/concepts-overview.mddocs/docs/Components/components-embedding-models.mddocs/docs/Components/components-helpers.mddocs/docs/Components/components-bundles.mddocs/docs/Concepts/concepts-components.mddocs/docs/Components/components-models.mddocs/docs/Components/components-processing.md
`docs/sidebars.js`: Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
docs/sidebars.js: Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
📄 Source: CodeRabbit Inference Engine (.cursor/rules/docs_development.mdc)
List of files the instruction was applied to:
docs/sidebars.js
`src/backend/**/*component*.py`: In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
src/backend/**/*component*.py: In your Python component class, set theiconattribute to a string matching the frontend icon mapping exactly (case-sensitive).
📄 Source: CodeRabbit Inference Engine (.cursor/rules/icons.mdc)
List of files the instruction was applied to:
src/backend/base/langflow/components/agents/mcp_component.py
🧠 Learnings (48)
📓 Common learnings
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
src/backend/base/langflow/components/data/sql_executor.py (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/backend/**/*component*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/backend/**/components/**/*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
docs/sidebars.js (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/sidebars.js : Sidebar navigation must be configured and updated in 'docs/sidebars.js' to reflect the current documentation structure.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Sidebar and navigation should be kept current to ensure users can easily find all documentation sections and cross-references.
docs/docs/Components/components-prompts.md (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
src/backend/base/langflow/components/processing/prompt.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
src/backend/base/langflow/components/models/language_model.py (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.837Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use 'MockLanguageModel' for testing language model components without external API calls.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
docs/docs/Components/components-io.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.837Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's 'Message' objects and chat functionality by asserting correct properties and structure.
src/backend/base/langflow/components/input_output/chat.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.837Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's 'Message' objects and chat functionality by asserting correct properties and structure.
src/backend/base/langflow/components/processing/lambda_filter.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
docs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.md (13)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.494Z
Learning: Applies to src/frontend/src/icons/**/*.{ts,tsx,js,jsx} : Use Lucide React for icons in frontend components.
Learnt from: dolfim-ibm
PR: langflow-ai/langflow#8394
File: src/frontend/src/icons/Docling/index.tsx:4-6
Timestamp: 2025-06-16T11:14:04.200Z
Learning: The Langflow codebase consistently uses `React.PropsWithChildren<{}>` as the prop type for all icon components using forwardRef, rather than `React.SVGProps<SVGSVGElement>`. This is an established pattern across hundreds of icon files in src/frontend/src/icons/.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Export custom icon components in React using React.forwardRef to ensure proper ref forwarding and compatibility with parent components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.494Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/frontend/src/icons/*/index.tsx : Create an `index.tsx` in your icon directory that exports your icon using `forwardRef` and passes the `isdark` prop.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/frontend/src/icons/*/* : Create a new directory for your icon in `src/frontend/src/icons/YourIconName/` and add your SVG as a React component (e.g., `YourIconName.jsx`) that uses the `isdark` prop to support both light and dark mode.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/frontend/src/icons/lazyIconImports.ts : Add your icon to the `lazyIconsMapping` object in `src/frontend/src/icons/lazyIconImports.ts` with a key that matches the backend icon string exactly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Custom SVG icon components in React should always support both light and dark mode by accepting an 'isdark' prop and adjusting colors accordingly.
src/backend/base/langflow/components/data/directory.py (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/tests/unit/components/**/*.py : Mirror the component directory structure in unit tests under src/backend/tests/unit/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/backend/**/*component*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/backend/**/components/**/*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
src/backend/base/langflow/components/logic/run_flow.py (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
src/backend/base/langflow/components/input_output/text.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
src/backend/base/langflow/components/processing/parser.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
src/backend/base/langflow/components/models/embedding_model.py (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/backend/**/*component*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
src/backend/base/langflow/components/data/webhook.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
src/backend/base/langflow/components/data/url.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
src/backend/base/langflow/components/processing/converter.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
src/backend/base/langflow/components/processing/split_text.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
src/backend/base/langflow/components/processing/structured_output.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
src/backend/base/langflow/components/processing/save_file.py (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
src/backend/base/langflow/components/data/file.py (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.837Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test backward compatibility across Langflow versions by mapping component files to supported versions using 'VersionComponentMapping'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
src/backend/base/langflow/components/processing/data_operations.py (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
docs/docs/Integrations/integrations-assemblyai.md (11)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.494Z
Learning: Applies to src/frontend/src/icons/**/*.{ts,tsx,js,jsx} : Use Lucide React for icons in frontend components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/frontend/src/icons/*/* : Create a new directory for your icon in `src/frontend/src/icons/YourIconName/` and add your SVG as a React component (e.g., `YourIconName.jsx`) that uses the `isdark` prop to support both light and dark mode.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/frontend/src/icons/*/index.tsx : Create an `index.tsx` in your icon directory that exports your icon using `forwardRef` and passes the `isdark` prop.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/frontend/src/icons/lazyIconImports.ts : Add your icon to the `lazyIconsMapping` object in `src/frontend/src/icons/lazyIconImports.ts` with a key that matches the backend icon string exactly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/frontend/src/icons/*/*.jsx : Always support both light and dark mode for custom icons by using the `isdark` prop in your SVG component.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Custom SVG icon components in React should always support both light and dark mode by accepting an 'isdark' prop and adjusting colors accordingly.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: Export custom icon components in React using React.forwardRef to ensure proper ref forwarding and compatibility with parent components.
src/backend/base/langflow/components/processing/llm_router.py (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
src/backend/base/langflow/components/data/news_search.py (2)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/backend/**/*component*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
docs/docs/Templates/blog-writer.md (8)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/blog/**/*.{md,mdx} : Blog posts must use the provided frontmatter and template, including fields for title, description, authors, date, and tags.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
docs/docs/Templates/basic-prompting.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
docs/docs/Templates/document-qa.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
docs/docs/Templates/memory-chatbot.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.837Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Test Langflow's 'Message' objects and chat functionality by asserting correct properties and structure.
docs/docs/Concepts/mcp-server.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Templates/financial-report-parser.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.494Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
docs/docs/Templates/vector-store-rag.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/docs/Components/components-memories.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Components/components-logic.md (6)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
docs/docs/Templates/simple-agent.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Support/release-notes.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
docs/docs/Concepts/concepts-flows.md (7)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.837Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.494Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
docs/docs/Concepts/concepts-publish.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.837Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
docs/docs/Concepts/concepts-playground.md (1)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
docs/docs/Components/components-tools.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
docs/docs/Concepts/concepts-overview.md (14)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Documentation content should be concise, with short paragraphs and parallel structure in lists for better readability.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Documentation content must follow the style guide: professional but approachable tone, second person voice, present tense, short paragraphs, sentence case headers, inline code with backticks, bold for UI elements, italic for emphasis, and parallel structure in lists.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.494Z
Learning: Applies to src/frontend/src/components/**/*FlowGraph.tsx : Use React Flow for flow graph visualization components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/testing.mdc:0-0
Timestamp: 2025-06-30T14:41:58.837Z
Learning: Applies to {src/backend/tests/**/*.py,tests/**/*.py} : Use predefined JSON flows and utility functions for flow testing (e.g., 'create_flow', 'build_flow', 'get_build_events', 'consume_and_assert_stream').
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-23T12:46:42.048Z
Learning: Custom React Flow node types should be implemented as memoized components, using Handle components for connection points and supporting optional icons and labels.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/tests/unit/**/*.py : Test component integration within flows using create_flow, build_flow, and get_build_events utilities
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Starter project files are auto-formatted after langflow run; these changes can be committed or ignored
docs/docs/Components/components-embedding-models.md (4)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
docs/docs/Components/components-bundles.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/frontend_development.mdc:0-0
Timestamp: 2025-06-30T14:40:29.494Z
Learning: Applies to src/frontend/src/icons/**/*.{ts,tsx,js,jsx} : Use Lucide React for icons in frontend components.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
docs/docs/Concepts/concepts-components.md (12)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-23T12:46:52.420Z
Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: Documentation content should be concise, with short paragraphs and parallel structure in lists for better readability.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/*.py : Add new backend components to the appropriate subdirectory under src/backend/base/langflow/components/
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/backend/**/components/**/*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/icons.mdc:0-0
Timestamp: 2025-06-30T14:40:50.836Z
Learning: Applies to src/backend/**/*component*.py : In your Python component class, set the `icon` attribute to a string matching the frontend icon mapping exactly (case-sensitive).
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Edit and test components in the UI first for fast iteration, then save to source
docs/docs/Components/components-models.md (5)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: ogabrielluiz
PR: langflow-ai/langflow#0
File: :0-0
Timestamp: 2025-06-26T19:43:18.260Z
Learning: In langflow custom components, the `module_name` parameter is now propagated through template building functions to add module metadata and code hashes to frontend nodes for better component tracking and debugging.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: All terminology such as 'Langflow', 'Component', 'Flow', 'API', and 'JSON' must be capitalized or uppercased as specified in the terminology section.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-23T12:46:29.953Z
Learning: When writing documentation for Langflow using Docusaurus, always use professional but approachable tone, second person voice for instructions, and present tense for current features.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
docs/docs/Components/components-processing.md (3)
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/components/**/*.{md,mdx} : Component documentation pages must follow the provided template, including sections for Overview, Configuration (Inputs/Outputs), Usage Example, and Common Issues.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-06-30T14:40:02.667Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/backend_development.mdc:0-0
Timestamp: 2025-06-30T14:39:17.428Z
Learning: Applies to src/backend/base/langflow/components/**/__init__.py : Update __init__.py with alphabetical imports when adding new components
🪛 LanguageTool
docs/docs/Templates/blog-writer.md
[style] ~56-~56: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...me** field, enter openai_api_key. 3. In the Value field, paste your OpenAI ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Templates/basic-prompting.md
[style] ~46-~46: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...me** field, enter openai_api_key. 3. In the Value field, paste your OpenAI ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Templates/document-qa.md
[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...me** field, enter openai_api_key. 3. In the Value field, paste your OpenAI ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Templates/memory-chatbot.md
[grammar] ~28-~28: The usual preposition to use after “fill” is “with”, not “a”. Did you mean “fill a part with”?
Context: ...nds them to the Prompt component to fill a part of the Template with context. To exam...
(FILL_OF_WITH)
[uncategorized] ~72-~72: Possible missing preposition found.
Context: ...D`. 2. Now, once you send a new message the Playground, you should have a new s...
(AI_HYDRA_LEO_MISSING_TO)
docs/docs/Concepts/mcp-server.md
[uncategorized] ~362-~362: It appears that a hyphen is missing (if ‘auto’ is not used in the context of ‘cars’).
Context: ...available for multiple MCP clients. To auto install your current Langflow project as an MCP...
(AUTO_HYPHEN)
docs/docs/Templates/financial-report-parser.md
[style] ~33-~33: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...me** field, enter openai_api_key. 3. In the Value field, paste your OpenAI ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[misspelling] ~36-~36: This word is normally spelled as one.
Context: ...Send**. The Chat Input component is pre-loaded with a sample financial report for demo...
(EN_COMPOUNDS_PRE_LOADED)
docs/docs/Templates/vector-store-rag.md
[style] ~61-~61: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...me** field, enter openai_api_key. 3. In the Value field, paste your OpenAI ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Components/components-memories.md
[formatting] ~18-~18: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ...re distinct from vector store components, because they are built specifically for storing...
(COMMA_BEFORE_BECAUSE)
docs/docs/Templates/simple-agent.md
[style] ~38-~38: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...me** field, enter openai_api_key. 3. In the Value field, paste your OpenAI ...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
docs/docs/Support/release-notes.md
[grammar] ~59-~59: Possible agreement error. The noun ‘bundle’ seems to be countable.
Context: ... BQ datasets. - Twelve Labs integration bundle. - NVIDIA system assistant component. ...
(CD_NN)
docs/docs/Concepts/concepts-publish.md
[duplication] ~39-~39: Possible typo: you repeated a word.
Context: ...://modelcontextprotocol.io/clients) can use use to take actions. For more information,...
(ENGLISH_WORD_REPEAT_RULE)
docs/docs/Concepts/concepts-playground.md
[typographical] ~25-~25: Usually, there’s no comma before “if”.
Context: ...ndividual components' def_build method, if it exists. If a component doesn't have ...
(IF_NO_COMMA)
docs/docs/Components/components-tools.md
[uncategorized] ~18-~18: Possible missing comma found.
Context: ... Legacy components are available for use but are no longer supported. To replace le...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/docs/Concepts/concepts-overview.md
[uncategorized] ~40-~40: Consider adding a hyphen.
Context: ...menu](#share-menu) are available in the upper right corner. ## Workspace The *workspace...
(TOP_LEFT_CORNER)
[style] ~50-~50: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... flow, similar to commenting in code. - Click <Icon name="LockOpen" aria-hidden="true...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[uncategorized] ~66-~66: Possible missing preposition found.
Context: ...ect-component.png) Message handles send text strings between components, so the...
(AI_HYDRA_LEO_MISSING_TO)
docs/docs/Components/components-embedding-models.md
[style] ~14-~14: ‘Prior to’ might be wordy. Consider a shorter alternative.
Context: ...ing the selected Large Language Model. Prior to Langflow 1.5, each embedding model prov...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[grammar] ~48-~48: A determiner cannot be combined with a possessive pronoun. Did you mean simply “the” or “your”?
Context: ...mponent-embedding-models.png) To query the your vector store, include [Chat Input](/com...
(A_MY)
docs/docs/Components/components-helpers.md
[uncategorized] ~19-~19: A punctuation mark might be missing here.
Context: ...thmetic expression to evaluate, such as 4*4*(33/22)+12-20. | Outputs | Name | Type | De...
(AI_EN_LECTOR_MISSING_PUNCTUATION)
[style] ~52-~52: ‘Prior to’ might be wordy. Consider a shorter alternative.
Context: ...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[formatting] ~58-~58: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ...ory is distinct from vector store memory, because it is built specifically for storing an...
(COMMA_BEFORE_BECAUSE)
[style] ~64-~64: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...in Langflow tables or external memory. In this example, one Message History c...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[uncategorized] ~106-~106: Possible missing comma found.
Context: ... Legacy components are available for use but are no longer supported. ### Create Li...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/docs/Concepts/concepts-components.md
[style] ~29-~29: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...-hidden="true" /> Inspect Output. To run a single component, click <Icon nam...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[uncategorized] ~244-~244: Possible missing comma found.
Context: ...egacy** components are available for use but are no longer supported. By default, le...
(AI_HYDRA_LEO_MISSING_COMMA)
docs/docs/Components/components-models.md
[style] ~14-~14: ‘Prior to’ might be wordy. Consider a shorter alternative.
Context: ...ing the selected Large Language Model. Prior to Langflow 1.5, each LLM and embedding mo...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
[style] ~78-~78: This phrase is redundant. Consider using “outside”.
Context: ... is less verbose, and lists its sources outside of the informative paragraph. For more inf...
(OUTSIDE_OF)
docs/docs/Components/components-processing.md
[uncategorized] ~16-~16: Loose punctuation mark.
Context: ...s the following columns: * text_input: The original text from the input DataFr...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~17-~17: Loose punctuation mark.
Context: ... the input DataFrame. * model_response: The model's response for each input. * ...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~18-~18: Loose punctuation mark.
Context: ...response for each input. * batch_index: The processing order, with a 0-based ...
(UNLIKELY_OPENING_PUNCTUATION)
[style] ~27-~27: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...n** component's DataFrame input. 3. Connect the Batch Run component's **Batch R...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~40-~40: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...-hidden="True" /> Run component. 8. To view your created DataFrame, in the **P...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~255-~255: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...mponent to the Judge LLM input. 3. Connect Chat Input and Chat Output comp...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~366-~366: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...Code** field, enter the Python code you want to execute. Use print() to see the outpu...
(REP_WANT_TO_VB)
[formatting] ~424-~424: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ...ll create the table using pd.DataFrame, because the pandas package is imported global...
(COMMA_BEFORE_BECAUSE)
[style] ~529-~529: ‘Prior to’ might be wordy. Consider a shorter alternative.
Context: ...
(EN_WORDINESS_PREMIUM_PRIOR_TO)
🪛 markdownlint-cli2 (0.17.2)
docs/docs/Templates/basic-prompting.md
42-42: Hard tabs
Column: 1
(MD010, no-hard-tabs)
44-44: Hard tabs
Column: 1
(MD010, no-hard-tabs)
45-45: Hard tabs
Column: 1
(MD010, no-hard-tabs)
46-46: Hard tabs
Column: 1
(MD010, no-hard-tabs)
47-47: Hard tabs
Column: 1
(MD010, no-hard-tabs)
docs/docs/Templates/financial-report-parser.md
34-34: Hard tabs
Column: 1
(MD010, no-hard-tabs)
36-36: Hard tabs
Column: 1
(MD010, no-hard-tabs)
37-37: Hard tabs
Column: 1
(MD010, no-hard-tabs)
docs/docs/Templates/vector-store-rag.md
25-25: Unordered list indentation
Expected: 2; Actual: 1
(MD007, ul-indent)
25-25: Hard tabs
Column: 1
(MD010, no-hard-tabs)
26-26: Unordered list indentation
Expected: 2; Actual: 1
(MD007, ul-indent)
26-26: Hard tabs
Column: 1
(MD010, no-hard-tabs)
57-57: Hard tabs
Column: 1
(MD010, no-hard-tabs)
59-59: Hard tabs
Column: 1
(MD010, no-hard-tabs)
60-60: Hard tabs
Column: 1
(MD010, no-hard-tabs)
61-61: Hard tabs
Column: 1
(MD010, no-hard-tabs)
62-62: Hard tabs
Column: 1
(MD010, no-hard-tabs)
docs/docs/Components/components-logic.md
236-236: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
243-243: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
docs/docs/Templates/simple-agent.md
25-25: Unordered list indentation
Expected: 2; Actual: 1
(MD007, ul-indent)
25-25: Hard tabs
Column: 1
(MD010, no-hard-tabs)
26-26: Unordered list indentation
Expected: 2; Actual: 1
(MD007, ul-indent)
26-26: Hard tabs
Column: 1
(MD010, no-hard-tabs)
docs/docs/Support/release-notes.md
43-43: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
44-44: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
45-45: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
46-46: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
47-47: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
49-49: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
50-50: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
51-51: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
52-52: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
53-53: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
56-56: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
64-64: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
65-65: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
68-68: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
76-76: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
77-77: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
78-78: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
79-79: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
82-82: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
docs/docs/Concepts/concepts-overview.md
91-91: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
92-92: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
93-93: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
94-94: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
95-95: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
docs/docs/Components/components-embedding-models.md
62-62: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
77-77: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
docs/docs/Components/components-helpers.md
21-21: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
122-122: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
143-143: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
docs/docs/Components/components-bundles.md
305-305: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
325-325: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
333-333: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
362-362: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
368-368: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
392-392: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
398-398: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
413-413: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
422-422: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
444-444: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
455-455: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
474-474: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
482-482: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
497-497: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
505-505: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
522-522: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
531-531: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
547-547: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
556-556: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
571-571: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
581-581: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
docs/docs/Components/components-processing.md
29-29: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
33-33: Table pipe style
Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
(MD055, table-pipe-style)
43-43: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
80-80: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
86-86: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
106-106: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🔇 Additional comments (40)
docs/docs/Concepts/concepts-objects.md (1)
200-206: LGTM – removal of dangling “See also” is correct.No other issues spotted in the modified tail of the file.
docs/docs/Components/components-io.md (1)
167-170: Update keeps instructions concise – verify list numbering.You removed the “click the flow name” step and rewrote step 4. Markdown renders ordered lists by the literal numbers, so the remaining steps (5, 6…) still make sense. Just eyeball in preview to ensure numbering isn’t off.
docs/sidebars.js (1)
378-382: Release notes link added – verify file path exists.
Support/release-notes.mdshould now be present and have the required front-matter. If not, the sidebar build will fail.Also, consider sorting Support items chronologically or alphabetically to minimise merge conflicts.
src/backend/base/langflow/components/data/sql_executor.py (1)
19-23:documentationattribute looks good; verify icon casing for consistencyThe new
documentationfield is a straightforward, correct addition.
While you are touching this header, double-check that the string literal inicon = "database"exactly matches the key used in the frontend icon map—most other components use PascalCase (e.g."MessagesSquare"). A casing mismatch silently breaks the icon in the UI.No change required if
"database"is indeed correct, but worth a quick grep acrossreact/src/iconsto confirm.docs/docs/Integrations/Notion/notion-agent-meeting-notes.md (1)
148-150: Nice UX improvement with the Play iconThe inline icon clarifies the action in the UI—good call.
src/backend/base/langflow/components/processing/prompt.py (1)
10-14: Attribute addition LGTMThe
documentationlink follows the new convention and the URL path is correct.src/backend/base/langflow/components/input_output/chat.py (1)
20-24: Consistent self-documentation added
ChatInput.documentationcorrectly points to the IO section. No issues spotted.src/backend/base/langflow/components/helpers/calculator_core.py (1)
12-16: Helper component now self-links—looks good
documentationattribute added; everything else unchanged.src/backend/base/langflow/components/data/web_search.py (1)
17-17: Documentation link attribute added—looks good.The addition follows the emerging convention across components and uses HTTPS, matching other entries. No further action needed.
src/backend/base/langflow/components/data/webhook.py (1)
12-12: Consistent and correctdocumentationURL.Attribute addition follows the same pattern as other components; URL looks valid. No issues spotted.
src/backend/base/langflow/components/input_output/text_output.py (1)
9-9: LGTM on the newdocumentationattribute.Change is minimal and consistent with the agreed-upon pattern.
src/backend/base/langflow/components/input_output/text.py (1)
9-9: Addition aligns with conventions—good to go.No concerns; URL and attribute placement are correct.
src/backend/base/langflow/components/processing/converter.py (1)
53-54:documentationattribute added – looks goodThe new attribute follows the emerging convention and has the correct slug.
src/backend/base/langflow/components/data/rss.py (1)
14-15:documentationattribute addition – OKThe link is valid and consistent with the new docs structure.
src/backend/base/langflow/components/agents/mcp_component.py (2)
82-82:documentationattribute addition – OKDirect link to MCP client docs improves discoverability.
83-83: Verify icon casing
icon = "Mcp"may not match the case-sensitive frontend mapping (commonly all-lowercase). Confirm that"Mcp"exists; otherwise change to"mcp"to avoid a missing icon.src/backend/base/langflow/components/data/file.py (1)
18-20: Consistency check: ensure newly-addeddocumentationattribute is recognised everywhereLGTM on the addition itself, but please confirm two things:
- All tooling that introspects components (e.g., automatic docs generator, frontend node builder) is already looking for
documentation(exact spelling).- The target URL resolves (
https://docs.langflow.org/components-data#file) before merge to avoid dead links.If both are true, no further action required.
docs/docs/Integrations/Google/integrations-setup-google-oauth-langflow.md (1)
7-8: Import path sanityMake sure the local alias
@site/src/components/iconexists in Docusaurus config on production; otherwise the build will fail.src/backend/base/langflow/components/data/api_request.py (1)
46-49: Good addition – verify link validityThe
documentationattribute improves discoverability. Please just double-check the URL slug (components-data#api-request) stays stable; a future docs restructure will otherwise break in-app links.src/backend/base/langflow/components/data/news_search.py (1)
13-16: Doc link added – looks correctNo functional impact. Ensure that the icon string
"newspaper"still matches the frontend mapping; nothing else to flag.src/backend/base/langflow/components/processing/batch_run.py (1)
18-20: Documentation link added—looks good.The new
documentationattribute is correctly introduced and follows the same pattern adopted across the code-base.
No functional impact detected.src/backend/base/langflow/components/input_output/chat_output.py (1)
23-26: Solid addition ofdocumentationattribute.The link is well-formed and consistent with other components. No other concerns.
src/backend/base/langflow/components/logic/run_flow.py (1)
14-17:documentationURL inserted correctly.Matches the new convention and poses no side-effects.
src/backend/base/langflow/components/processing/llm_router.py (1)
18-21: Documentation field addition accepted.The change is straightforward; behaviour remains unchanged.
src/backend/base/langflow/components/logic/conditional_router.py (1)
9-12: Good—component now links to docs.No issues spotted with the new attribute.
src/backend/base/langflow/components/data/directory.py (1)
12-12: ✅ Documentation Link VerifiedThe URL
https://docs.langflow.org/components-data#directoryreturns HTTP 200 and the page includes an<h2 id="directory">section, confirming the Directory component documentation exists as expected.
Change approved.src/backend/base/langflow/components/processing/parser.py (1)
13-13: LGTM!The documentation URL addition is consistent with the established pattern and properly typed.
src/backend/base/langflow/components/data/url.py (2)
20-23: LGTM!The regex pattern reformatting improves readability without changing functionality. The pattern remains logically equivalent to the original multiline version.
39-39: LGTM!The documentation URL addition follows the consistent pattern and is properly typed.
src/backend/base/langflow/components/processing/split_text.py (1)
14-14: LGTM!The documentation URL addition is consistent with the established pattern and correctly uses hyphenation for the multi-word component name.
src/backend/base/langflow/components/models/embedding_model.py (1)
23-23: Documentation URL pattern is correct and consistentThe URL
https://docs.langflow.org/components-embedding-modelsreturns a 200 response and matches the pattern used by the LanguageModelComponent (https://docs.langflow.org/components-models). No fragment identifier is required for dedicated group pages. No changes needed.src/backend/base/langflow/components/helpers/current_date.py (1)
14-14: Addition ofdocumentationattribute looks correctThe new
documentationattribute follows the emerging convention and introduces no functional side effects. ✅src/backend/base/langflow/components/helpers/memory.py (1)
19-19: Documentation link added – good to goThe link format and placement are consistent with other components.
src/backend/base/langflow/components/processing/save_file.py (1)
23-23:documentationfield added as expectedNo issues spotted; the change is non-breaking.
src/backend/base/langflow/components/processing/lambda_filter.py (1)
19-19: Link attribute addition is fineMatches the established pattern; nothing further required.
src/backend/base/langflow/components/processing/structured_output.py (1)
21-21: Structured Output documentation URL added – looks goodConsistent with the rest of the PR.
docs/docs/Components/components-prompts.md (1)
14-18: Link fragment: ensure/basic-promptingpage existsThe new link points to
/basic-prompting. Please double-check that:
- The page slug exactly matches (case-sensitive).
- The page sits under
docs/docs/**so that the generated URL is correct.A quick
npm run docusaurus buildbefore merging will catch broken internal links.docs/docs/Templates/simple-agent.md (1)
30-41: Fix header case and replace hard tabs with spaces to satisfy markdown-lintTabs trigger
MD010and wrong indent triggersMD007.-## Run the simple agent flow +## Run the Simple Agent Flow ... - Optionally, create a [global variable](/configuration-global-variables) for the **OpenAI API key**. + Optionally, create a [Global Variable](/configuration-global-variables) for the **OpenAI API Key**. - - 1. In the **OpenAI API Key** field, click <Icon name="Globe" aria-hidden="True" /> **Globe**, and then click **Add New Variable**. - 2. In the **Variable Name** field, enter `openai_api_key`. - 3. In the **Value** field, paste your OpenAI API Key (`sk-...`). - 4. Click **Save Variable**. + 1. In the **OpenAI API Key** field, click <Icon name="Globe" aria-hidden="true" /> **Globe**, and then click **Add New Variable**. + 2. In the **Variable Name** field, enter `openai_api_key`. + 3. In the **Value** field, paste your OpenAI API key (`sk-...`). + 4. Click **Save Variable**.⛔ Skipped due to learnings
Learnt from: CR PR: langflow-ai/langflow#0 File: .cursor/rules/docs_development.mdc:0-0 Timestamp: 2025-06-23T12:46:29.953Z Learning: Headers in documentation should use sentence case, and formatting should include inline code with backticks, bold for UI elements, and italic for emphasis.Learnt from: CR PR: langflow-ai/langflow#0 File: .cursor/rules/docs_development.mdc:0-0 Timestamp: 2025-06-30T14:40:02.667Z Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize 'Langflow', 'Component', and 'Flow' when referring to Langflow concepts; always uppercase 'API' and 'JSON'.docs/docs/Concepts/concepts-components.md (1)
51-61: Table pipes fail markdown-lint rule MD055
Header row and some body rows are missing the trailing|. This breaks renderer alignment and triggers CI markdown-lint.-| Data type | Handle color | Handle | +| Data type | Handle color | Handle |(ensure a final pipe on every row)
⛔ Skipped due to learnings
Learnt from: CR PR: langflow-ai/langflow#0 File: .cursor/rules/icons.mdc:0-0 Timestamp: 2025-06-23T12:46:52.420Z Learning: When implementing a new component icon in Langflow, ensure the icon name is clear, recognizable, and used consistently across both backend (Python 'icon' attribute) and frontend (React/TypeScript mapping).Learnt from: CR PR: langflow-ai/langflow#0 File: .cursor/rules/icons.mdc:0-0 Timestamp: 2025-06-30T14:40:50.836Z Learning: Use clear, recognizable, and consistent icon names for both backend and frontend (e.g., 'AstraDB', 'Postgres', 'OpenAI').Learnt from: CR PR: langflow-ai/langflow#0 File: .cursor/rules/icons.mdc:0-0 Timestamp: 2025-06-23T12:46:52.420Z Learning: Custom SVG icon components in React should always support both light and dark mode by accepting an 'isdark' prop and adjusting colors accordingly.docs/docs/Components/components-processing.md (1)
638-656: Deprecated “Multiple” flag needs clarification
You note “This feature is deprecated” but still document default behaviour. Consider adding an admonition explaining the planned removal or alternative, to avoid user confusion.:::warning The **Multiple** column is deprecated and will be removed in a future release. Avoid relying on it; use list-typed fields instead. :::
| --- | ||
|
|
||
| Langflow integrates with the [Google Vertex AI API](https://console.cloud.google.com/marketplace/product/google/aiplatform.googleapis.com) for authenticating the [Vertex AI embeddings model](/components-embedding-models#vertexai-embeddings) and [Vertex AI](/components-models#vertexai) components. | ||
| Langflow integrates with the [Google Vertex AI API](https://console.cloud.google.com/marketplace/product/google/aiplatform.googleapis.com) for authenticating the [Vertex AI embeddings model](/components-bundle-components#vertexai-embeddings) and [Vertex AI](/components-bundle-components#vertexai) components. |
There was a problem hiding this comment.
Broken internal links – update slug
The updated paths use /components-bundle-components#…, but the new page is components-bundles.md, so the slug is /components-bundles. Both links will 404.
-[Vertex AI embeddings model](/components-bundle-components#vertexai-embeddings)
+[Vertex AI embeddings model](/components-bundles#vertexai-embeddings)
-[Vertex AI](/components-bundle-components#vertexai)
+[Vertex AI](/components-bundles#vertexai)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Langflow integrates with the [Google Vertex AI API](https://console.cloud.google.com/marketplace/product/google/aiplatform.googleapis.com) for authenticating the [Vertex AI embeddings model](/components-bundle-components#vertexai-embeddings) and [Vertex AI](/components-bundle-components#vertexai) components. | |
| Langflow integrates with the [Google Vertex AI API](https://console.cloud.google.com/marketplace/product/google/aiplatform.googleapis.com) for authenticating the [Vertex AI embeddings model](/components-bundles#vertexai-embeddings) and [Vertex AI](/components-bundles#vertexai) components. |
🤖 Prompt for AI Agents
In
docs/docs/Integrations/Google/integrations-setup-google-cloud-vertex-ai-langflow.md
at line 6, the internal links use the outdated slug
/components-bundle-components which causes 404 errors. Update both links to use
the correct slug /components-bundles to match the new page name
components-bundles.md.
| import Icon from "@site/src/components/icon"; | ||
|
|
There was a problem hiding this comment.
MDX syntax inside .md file will break the docs build
The import Icon from "@site/src/components/icon"; line turns this into MDX, but the file extension is still .md.
Docusaurus will treat it as plain Markdown and fail with a parsing error.
Rename the file to .mdx or drop the JSX import.
-integrations-assemblyai.md
+integrations-assemblyai.mdxCommittable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In docs/docs/Integrations/integrations-assemblyai.md around lines 6 to 7, the
import statement for the Icon component introduces MDX syntax in a file with a
.md extension, causing the docs build to fail. To fix this, either rename the
file extension from .md to .mdx to properly support MDX syntax or remove the
import statement and any JSX usage to keep the file as plain Markdown.
| Build a **Basic prompting** flow with [Language model](/components-models), [Prompt](/components-prompts), and [Chat I/O](/components-io) components. | ||
|
|
||
| Prompts serve as the inputs to a large language model (LLM), acting as the interface between human instructions and computational tasks. |
There was a problem hiding this comment.
MDX in .md – same build-blocking issue
This file also imports the Icon React component even though it carries a .md extension.
Rename to .mdx (or remove JSX) to prevent the documentation build from failing.
🤖 Prompt for AI Agents
In docs/docs/Templates/basic-prompting.md around lines 8 to 10, the file imports
a React component which is not supported in `.md` files and causes build
failures. Rename the file extension from `.md` to `.mdx` to enable JSX support,
or alternatively remove the JSX imports and usage to keep it as a pure markdown
file and avoid build issues.
| This flow extends the Basic Prompting flow with the [URL](/components-data#url) and [Parser](/components-processing#parser) components that fetch content from multiple URLs and convert the loaded data into plain text. | ||
|
|
||
| OpenAI uses this loaded data to generate a blog post, as instructed by the **Text Input** and **Prompt** components. | ||
| The [Language model](/components-models) component uses this loaded data to generate a blog post, as instructed by the [Text input](/components-io#text-input) and [Prompt](components-prompts) components. |
There was a problem hiding this comment.
Fix broken internal link to Prompt component
Relative link lacks leading slash, resulting in /Templates/components-prompts 404.
-The [Language model](/components-models) component uses this loaded data to generate a blog post, as instructed by the [Text input](/components-io#text-input) and [Prompt](components-prompts) components.
+The [Language model](/components-models) component uses this loaded data to generate a blog post, as instructed by the [Text input](/components-io#text-input) and [Prompt](/components-prompts) components.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| The [Language model](/components-models) component uses this loaded data to generate a blog post, as instructed by the [Text input](/components-io#text-input) and [Prompt](components-prompts) components. | |
| The [Language model](/components-models) component uses this loaded data to generate a blog post, as instructed by the [Text input](/components-io#text-input) and [Prompt](/components-prompts) components. |
🤖 Prompt for AI Agents
In docs/docs/Templates/blog-writer.md at line 12, the internal link to the
Prompt component is missing a leading slash, causing a broken link. Fix this by
adding a leading slash to the relative URL so it correctly points to
/components-prompts instead of /Templates/components-prompts.
| 1. Add your **OpenAI API key** to the **Language model** model component. | ||
| Optionally, create a [global variable](/configuration-global-variables) for the **OpenAI API key**. | ||
|
|
||
| 1. In the **OpenAI API Key** field, click <Icon name="Globe" aria-hidden="True" /> **Globe**, and then click **Add New Variable**. |
There was a problem hiding this comment.
Use lowercase aria-hidden value
aria-hidden must be lowercase "true" to be valid HTML.
-<Icon name="Globe" aria-hidden="True" />
+<Icon name="Globe" aria-hidden="true" />📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| 1. In the **OpenAI API Key** field, click <Icon name="Globe" aria-hidden="True" /> **Globe**, and then click **Add New Variable**. | |
| 1. In the **OpenAI API Key** field, click <Icon name="Globe" aria-hidden="true" /> **Globe**, and then click **Add New Variable**. |
🤖 Prompt for AI Agents
In docs/docs/Templates/financial-report-parser.md at line 31, the aria-hidden
attribute value is incorrectly capitalized as "True". Change the value of
aria-hidden to lowercase "true" to comply with valid HTML standards.
| import Icon from "@site/src/components/icon"; | ||
|
|
There was a problem hiding this comment.
.md file embeds JSX – convert to .mdx or drop JSX import
The file is saved with a .md extension but contains MDX-only syntax (import Icon … and <Icon …/> usages).
Docusaurus processes plain .md as Markdown by default; JSX will be ignored and the build will fail.
-// keep the JSX but rename the file
-docs/docs/Components/components-bundles.md
+docs/docs/Components/components-bundles.mdxAlternatively, remove the Icon import/usage if MDX is not required.
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In docs/docs/Components/components-bundles.md around lines 6 to 7, the file uses
JSX syntax but has a .md extension, which causes build failures because .md
files do not support JSX. To fix this, rename the file extension from .md to
.mdx to enable MDX processing, or alternatively, remove the JSX import and usage
if you want to keep the file as plain Markdown.
| import Icon from "@site/src/components/icon"; | ||
|
|
||
| # Embeddings models in Langflow | ||
|
|
||
| Embeddings models convert text into numerical vectors. These embeddings capture the semantic meaning of the input text, and allow LLMs to understand context. | ||
|
|
||
| Refer to your specific component's documentation for more information on parameters. | ||
|
|
||
| ## Use an embeddings model component in a flow | ||
|
|
||
| In this example of a document ingestion pipeline, the **OpenAI** embeddings model is connected to a vector database. The component converts the text chunks into vectors and stores them in the vector database. The vectorized data can be used to inform AI workloads like chatbots, similarity searches, and agents. | ||
|
|
||
| This embeddings component uses an OpenAI API key for authentication. Refer to your specific embeddings component's documentation for more information on authentication. | ||
|
|
||
|  | ||
|
|
||
| ## AI/ML | ||
|
|
||
| This component generates embeddings using the [AI/ML API](https://docs.aimlapi.com/api-overview/embeddings). | ||
|
|
||
| <details> | ||
| <summary>Parameters</summary> | ||
|
|
||
| **Inputs** | ||
|
|
||
| | Name | Type | Description | | ||
| |------|------|-------------| | ||
| | model_name | String | The name of the AI/ML embedding model to use. | | ||
| | aiml_api_key | SecretString | The API key required for authenticating with the AI/ML service. | | ||
|
|
||
| **Outputs** | ||
|
|
||
| | Name | Type | Description | | ||
| |------|------|-------------| | ||
| | embeddings | Embeddings | An instance of `AIMLEmbeddingsImpl` for generating embeddings. | | ||
|
|
||
| </details> | ||
|
|
||
| ## Amazon Bedrock Embeddings | ||
|
|
||
| This component is used to load embedding models from [Amazon Bedrock](https://aws.amazon.com/bedrock/). | ||
|
|
||
| <details> | ||
| <summary>Parameters</summary> | ||
|
|
||
| **Inputs** | ||
|
|
||
| | Name | Type | Description | | ||
| |------|------|-------------| | ||
| | credentials_profile_name | String | The name of the AWS credentials profile in `~/.aws/credentials` or `~/.aws/config`, which has access keys or role information. | | ||
| | model_id | String | The ID of the model to call, such as `amazon.titan-embed-text-v1`. This is equivalent to the `modelId` property in the `list-foundation-models` API. | | ||
| | endpoint_url | String | The URL to set a specific service endpoint other than the default AWS endpoint. | | ||
| | region_name | String | The AWS region to use, such as `us-west-2`. Falls back to the `AWS_DEFAULT_REGION` environment variable or region specified in `~/.aws/config` if not provided. | | ||
|
|
||
| **Outputs** | ||
|
|
||
| | Name | Type | Description | | ||
| |------|------|-------------| | ||
| | embeddings | Embeddings | An instance for generating embeddings using Amazon Bedrock. | | ||
|
|
||
| </details> | ||
|
|
||
| ## Astra DB vectorize | ||
|
|
||
| :::important |
There was a problem hiding this comment.
Same JSX issue as above
Rename the file to .mdx or strip the Icon import/JSX to avoid a docs build break.
🤖 Prompt for AI Agents
In docs/docs/Components/components-embedding-models.md around lines 6 to 8, the
file contains JSX code and an import statement for the Icon component, which
causes the documentation build to break because the file has a .md extension. To
fix this, either rename the file extension from .md to .mdx to support JSX or
remove the Icon import and any JSX usage from the file to keep it as pure
markdown.
| --- | ||
| title: Components overview | ||
| title: Components | ||
| slug: /concepts-components | ||
| --- |
There was a problem hiding this comment.
Front-matter lacks required description field
The docs style-guide mandates at least title and description in every markdown front-matter block. Missing description will cause Docusaurus builds to fail.
---
title: Components
+description: Overview of Langflow Components and how to use, configure, and version them in a Flow.
slug: /concepts-components
---📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| --- | |
| title: Components overview | |
| title: Components | |
| slug: /concepts-components | |
| --- | |
| --- | |
| title: Components | |
| description: Overview of Langflow Components and how to use, configure, and version them in a Flow. | |
| slug: /concepts-components | |
| --- |
🤖 Prompt for AI Agents
In docs/docs/Concepts/concepts-components.md at lines 1 to 4, the front-matter
block is missing the required description field. Add a description field with a
brief summary of the page content below the title to comply with the docs
style-guide and prevent Docusaurus build failures.
| A component is a single building block within a flow with inputs, outputs, functions, and parameters that define its functionality. A single component is like a class within a larger application. | ||
|
|
||
| :::tip | ||
| Langflow provides keyboard shortcuts for the **Workspace**. | ||
| ## Component menus | ||
|
|
||
| In the Langflow header, click your profile icon, select **Settings**, and then click **Shortcuts** to view the available shortcuts. | ||
| ::: | ||
|
|
||
| ## Add a component to a flow {#component-menus} | ||
|
|
||
| To add a component to a flow, drag the component from the **Components** menu to the [**Workspace**](/concepts-overview). | ||
|
|
||
| The **Components** menu is organized by component type, and some components are hidden by default: | ||
|
|
||
| * **Beta components**: These are Langflow's core components. They are grouped by purpose, such as **Inputs** or **Data**. Be aware that these components are in beta and not suitable for production workloads. | ||
| * **Legacy components**: You can still use these components, but they are no longer supported. Legacy components are hidden by default; click <Icon name="SlidersHorizontal" aria-hidden="true" /> **Component settings** to expose legacy components. | ||
| * **Bundles**: These components support specific integrations, and they are grouped by provider. | ||
|
|
||
| ### Configure a component | ||
|
|
||
| After adding a component to a flow, configure the component's parameters and connect it to the other components in your flows. | ||
| To add a component to a flow, drag it from the **Components** menu to the [**Workspace**](/concepts-overview), and then configure the component's parameters and connect it to the other components in your flows. | ||
|
|
||
| Each component has inputs, outputs, parameters, and controls related to the component's purpose. | ||
| By default, components show only required and common options. | ||
| To access additional settings and controls, including meta settings, use the component's header menu. | ||
|
|
||
| To access a component's header menu, click the component in your **Workspace**. | ||
| To access a component's header menu, select the component in your **Workspace**. | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Inconsistent capitalization of the Langflow term “Component”
Style-guide: always capitalize ‘Component’ when referring to the Langflow concept.
Here it appears in lowercase multiple times (“component”, “component’s”, “component menus”…). Do a quick search-replace for the entire file to ensure consistency.
-A component is a single building block within a flow
+A **Component** is a single building block within a **Flow**Repeat for other instances.
Also applies to: 22-29
🤖 Prompt for AI Agents
In docs/docs/Concepts/concepts-components.md around lines 8 to 19 and 22 to 29,
the term "component" is inconsistently capitalized when referring to the
Langflow concept. Update all instances of "component", "component’s", "component
menus", and similar terms to "Component", "Component’s", "Component menus",
etc., to follow the style guide. Perform a search and replace throughout the
file to ensure all references to the Langflow concept are capitalized
consistently.
| Processing components process and transform data within a flow, like converting `Data` to text with a [Parser](#parser) component, filtering data with natural language with the [Smart function](#smart-function), or saving data to your local machine with [Save File](#save-file). | ||
|
|
||
| ## Use a processing component in a flow | ||
| ## Batch Run | ||
|
|
||
| The **Split Text** processing component in this flow splits the incoming [Data](/concepts-objects) into chunks to be embedded into the vector store component. | ||
| The **Batch Run** component runs a language model over **each row** of a [DataFrame](/concepts-objects#dataframe-object) text column and returns a new DataFrame with the original text and an LLM response. | ||
|
|
||
| The component offers control over chunk size, overlap, and separator, which affect context and granularity in vector store retrieval results. | ||
| The response contains the following columns: |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Capitalize “Component” when used as a Langflow concept
Processing components process and transform data … → Processing Components …. Apply throughout the document (e.g., “Batch Run component”, “Data operations component”, etc.) to meet terminology rules.
🤖 Prompt for AI Agents
In docs/docs/Components/components-processing.md around lines 8 to 14, the term
"component" is used in lowercase when referring to Langflow concepts. Update all
instances of "component" to "Component" to follow the capitalization convention
for Langflow concepts throughout the document, including phrases like "Batch Run
component" and "Data operations component."
|
Build failure! ❌
|
|
Superseded by #8850 |
1 participant
New PR because of all the Code Red changes.
Supersedes #8589
Summary by CodeRabbit
Documentation
New Features