fix: Rename Component- Smart Function into Smart Transform#10003
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughThe PR updates documentation to replace references to “Smart Function” with “Smart Transform” across multiple component docs and concepts. Additionally, it renames metadata strings (display name, documentation URL, and name) in LambdaFilterComponent to “Smart Transform.” No logic or control-flow changes are introduced. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (7 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
deon-sanchez
changed the title
github-actions
Bot
added
bug
github-actions
Bot
added
bug
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 8
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (25)
docs/docs/Components/bundles-aiml.mdx(1 hunks)docs/docs/Components/bundles-amazon.mdx(1 hunks)docs/docs/Components/bundles-anthropic.mdx(1 hunks)docs/docs/Components/bundles-azure.mdx(1 hunks)docs/docs/Components/bundles-baidu.mdx(1 hunks)docs/docs/Components/bundles-cohere.mdx(1 hunks)docs/docs/Components/bundles-deepseek.mdx(1 hunks)docs/docs/Components/bundles-groq.mdx(1 hunks)docs/docs/Components/bundles-huggingface.mdx(1 hunks)docs/docs/Components/bundles-ibm.mdx(1 hunks)docs/docs/Components/bundles-lmstudio.mdx(1 hunks)docs/docs/Components/bundles-maritalk.mdx(1 hunks)docs/docs/Components/bundles-mistralai.mdx(1 hunks)docs/docs/Components/bundles-novita.mdx(1 hunks)docs/docs/Components/bundles-ollama.mdx(1 hunks)docs/docs/Components/bundles-openai.mdx(1 hunks)docs/docs/Components/bundles-openrouter.mdx(1 hunks)docs/docs/Components/bundles-perplexity.mdx(1 hunks)docs/docs/Components/bundles-sambanova.mdx(1 hunks)docs/docs/Components/bundles-vertexai.mdx(1 hunks)docs/docs/Components/bundles-xai.mdx(1 hunks)docs/docs/Components/components-models.mdx(2 hunks)docs/docs/Components/components-processing.mdx(7 hunks)docs/docs/Concepts/data-types.mdx(1 hunks)src/lfx/src/lfx/components/processing/lambda_filter.py(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/docs/**/*.{md,mdx}
📄 CodeRabbit inference engine (.cursor/rules/docs_development.mdc)
docs/docs/**/*.{md,mdx}: All documentation content must be written in Markdown or MDX files located under docs/docs/, following the prescribed directory structure for guides, reference, how-to, concepts, and API documentation.
All documentation Markdown and MDX files must begin with a frontmatter block including at least title and description fields.
Use admonitions (:::tip, :::warning, :::danger) in Markdown/MDX files to highlight important information, warnings, or critical issues.
All images referenced in documentation must include descriptive alt text for accessibility.
All code examples included in documentation must be tested and verified to work as shown.
Internal links in documentation must be functional and not broken.
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, Flow, and uppercase API and JSON.
Files:
docs/docs/Components/bundles-perplexity.mdxdocs/docs/Components/bundles-mistralai.mdxdocs/docs/Components/bundles-openrouter.mdxdocs/docs/Components/bundles-anthropic.mdxdocs/docs/Components/bundles-azure.mdxdocs/docs/Components/bundles-sambanova.mdxdocs/docs/Components/components-processing.mdxdocs/docs/Components/bundles-ollama.mdxdocs/docs/Components/bundles-novita.mdxdocs/docs/Components/bundles-lmstudio.mdxdocs/docs/Concepts/data-types.mdxdocs/docs/Components/bundles-vertexai.mdxdocs/docs/Components/bundles-deepseek.mdxdocs/docs/Components/bundles-amazon.mdxdocs/docs/Components/bundles-aiml.mdxdocs/docs/Components/bundles-huggingface.mdxdocs/docs/Components/components-models.mdxdocs/docs/Components/bundles-openai.mdxdocs/docs/Components/bundles-cohere.mdxdocs/docs/Components/bundles-groq.mdxdocs/docs/Components/bundles-ibm.mdxdocs/docs/Components/bundles-maritalk.mdxdocs/docs/Components/bundles-baidu.mdxdocs/docs/Components/bundles-xai.mdx
🧠 Learnings (2)
📓 Common learnings
Learnt from: CR
PR: langflow-ai/langflow#0
File: .cursor/rules/docs_development.mdc:0-0
Timestamp: 2025-07-18T18:26:42.027Z
Learning: Applies to docs/docs/**/*.{md,mdx} : Use consistent terminology: always capitalize Langflow, Component, Flow, and uppercase API and JSON.
📚 Learning: 2025-08-11T16:52:26.755Z
Learnt from: edwinjosechittilappilly
PR: langflow-ai/langflow#9336
File: src/backend/base/langflow/base/models/openai_constants.py:29-33
Timestamp: 2025-08-11T16:52:26.755Z
Learning: The "gpt-5-chat-latest" model in the OpenAI models configuration does not support tool calling, so tool_calling should be set to False for this model in src/backend/base/langflow/base/models/openai_constants.py.
Applied to files:
docs/docs/Components/bundles-aiml.mdx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Validate PR
- GitHub Check: Test Docs Build / Test Docs Build
- GitHub Check: build-and-deploy
🔇 Additional comments (18)
src/lfx/src/lfx/components/processing/lambda_filter.py (1)
17-22: Renamed metadata reads wellThe display name, documentation link, and name now consistently reflect “Smart Transform.” Looks good.
docs/docs/Components/bundles-anthropic.mdx (1)
22-22: Terminology update looks correct.Renaming the example component to Smart Transform keeps this doc aligned with the updated component naming everywhere else.
docs/docs/Components/bundles-ollama.mdx (1)
35-35: Consistent Smart Transform reference.This keeps the bundle guidance in sync with the new component name.
docs/docs/Components/bundles-huggingface.mdx (1)
23-23: Smart Transform rename looks good.The wording now matches the updated processing component terminology.
docs/docs/Components/bundles-novita.mdx (1)
19-19: Novita bundle copy updated appropriately.Reference to Smart Transform is consistent with the broader rename.
docs/docs/Concepts/data-types.mdx (1)
143-143: Data types doc reflects new name.Connecting the Language Model output to the Smart Transform component matches the updated terminology.
docs/docs/Components/bundles-vertexai.mdx (1)
23-23: Vertex AI guidance aligns with rename.The Smart Transform mention keeps the instructions current.
docs/docs/Components/bundles-openai.mdx (1)
23-23: OpenAI doc uses the new component name.The Smart Transform reference matches the standardized terminology.
docs/docs/Components/components-models.mdx (2)
98-99: Driver tab link updated correctly.Pointing to Smart Transform keeps the docs coherent after the rename.
158-162: Output type description matches new naming.Both mentions of Smart Transform reflect the current component label.
docs/docs/Components/bundles-baidu.mdx (1)
18-18: Terminology alignment looks good.Thanks for updating the reference to Smart Transform here—it keeps the bundle doc terminology consistent with the renamed component.
docs/docs/Components/bundles-openrouter.mdx (1)
21-21: Renamed reference confirmed.The switch to Smart Transform keeps the OpenRouter docs in sync with the new component name.
docs/docs/Components/bundles-deepseek.mdx (1)
21-21: Consistent naming retained.The DeepSeek bundle now correctly points to Smart Transform, matching the broader terminology update.
docs/docs/Components/bundles-perplexity.mdx (1)
21-21: Terminology update verified.Good to see the Perplexity bundle reflects Smart Transform in this guidance.
docs/docs/Components/bundles-sambanova.mdx (1)
21-21: Smart Transform reference confirmed.This keeps the SambaNova docs consistent with the renamed component.
docs/docs/Components/bundles-groq.mdx (1)
21-21: Groq docs align with new naming.The updated wording correctly points to Smart Transform.
docs/docs/Components/bundles-xai.mdx (1)
21-21: xAI bundle wording looks good.Smart Transform terminology is now consistent here as well.
docs/docs/Components/bundles-cohere.mdx (1)
21-21: Cohere bundle updated correctly.Thanks for keeping the reference aligned with the Smart Transform rename.
| Specifically, the **Language Model** output is an instance of [`ChatBedrock`](https://python.langchain.com/docs/integrations/chat/bedrock/) configured according to the component's parameters. | ||
|
|
||
| Use the **Language Model** output when you want to use an Amazon Bedrock model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Function** component. | ||
| Use the **Language Model** output when you want to use an Amazon Bedrock model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Capitalize “Component” per style guide
Please capitalize “Component” to meet the required terminology conventions. As per coding guidelines
-Use the **Language Model** output when you want to use an Amazon Bedrock model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component.
+Use the **Language Model** output when you want to use an Amazon Bedrock model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component.📝 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.
| Use the **Language Model** output when you want to use an Amazon Bedrock model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. | |
| Use the **Language Model** output when you want to use an Amazon Bedrock model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component. |
🤖 Prompt for AI Agents
In docs/docs/Components/bundles-amazon.mdx around line 20, the word “component”
in the sentence should be capitalized to “Component” per the style guide; update
the sentence so both occurrences ("component" and any other instance in that
line) use "Component" (e.g., "Agent" or "Smart Transform Component") to match
terminology conventions.
| Specifically, the **Language Model** output is an instance of [`AzureChatOpenAI`](https://python.langchain.com/docs/integrations/chat/azure_chat_openai/) configured according to the component's parameters. | ||
|
|
||
| Use the **Language Model** output when you want to use an Azure OpenAI model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Function** component. | ||
| Use the **Language Model** output when you want to use an Azure OpenAI model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Capitalize “Component” per style guide
Capitalize “Component” in both spots to keep terminology consistent. As per coding guidelines
-Use the **Language Model** output when you want to use an Azure OpenAI model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component.
+Use the **Language Model** output when you want to use an Azure OpenAI model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component.📝 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.
| Use the **Language Model** output when you want to use an Azure OpenAI model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. | |
| Use the **Language Model** output when you want to use an Azure OpenAI model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component. |
🤖 Prompt for AI Agents
In docs/docs/Components/bundles-azure.mdx around line 20, the word “component”
appears twice and should be capitalized per the style guide; update both
occurrences to “Component” so the sentence reads: "Use the **Language Model**
output when you want to use an Azure OpenAI model as the LLM for another
LLM-driven Component, such as an **Agent** or **Smart Transform** Component."
| Use the **Language Model** output when you want to use an IBM watsonx.ai model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. | ||
| For more information, see [Language model components](/components-models). |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Capitalize “Component” per style guide
Both “component” instances here should be capitalized to follow the documentation guidelines. As per coding guidelines
-Use the **Language Model** output when you want to use an IBM watsonx.ai model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component.
+Use the **Language Model** output when you want to use an IBM watsonx.ai model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component.📝 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.
| Use the **Language Model** output when you want to use an IBM watsonx.ai model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. | |
| For more information, see [Language model components](/components-models). | |
| Use the **Language Model** output when you want to use an IBM watsonx.ai model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component. | |
| For more information, see [Language model components](/components-models). |
🤖 Prompt for AI Agents
In docs/docs/Components/bundles-ibm.mdx around lines 47 to 48, the two
occurrences of the word "component" should be capitalized to follow the
documentation style guide; update both instances to "Component" (e.g.,
"LLM-driven Component" and "Smart Transform Component") and verify surrounding
punctuation/spacing remains correct.
| It can output either a **Model Response** ([`Message`](/data-types#message)) or a **Language Model** ([`LanguageModel`](/data-types#languagemodel)). | ||
|
|
||
| Use the **Language Model** output when you want to use an LM Studio model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Function** component. | ||
| Use the **Language Model** output when you want to use an LM Studio model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Capitalize “Component” per style guide
Style guide requires capitalizing “Component.” Please adjust to keep terminology consistent. As per coding guidelines
-Use the **Language Model** output when you want to use an LM Studio model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component.
+Use the **Language Model** output when you want to use an LM Studio model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component.📝 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.
| Use the **Language Model** output when you want to use an LM Studio model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. | |
| Use the **Language Model** output when you want to use an LM Studio model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component. |
🤖 Prompt for AI Agents
In docs/docs/Components/bundles-lmstudio.mdx around line 20, the word
"component" is not capitalized per the style guide; update the sentence to
capitalize "Component" wherever it refers to the product term (e.g., "Agent" or
"Smart Transform Component") so terminology is consistent with the documentation
style.
| It can output either a **Model Response** ([`Message`](/data-types#message)) or a **Language Model** ([`LanguageModel`](/data-types#languagemodel)). | ||
|
|
||
| Use the **Language Model** output when you want to use a MariTalk model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Function** component. | ||
| Use the **Language Model** output when you want to use a MariTalk model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Capitalize “Component” per style guide
Need to capitalize “Component” in both instances to comply with the style guide. As per coding guidelines
-Use the **Language Model** output when you want to use a MariTalk model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component.
+Use the **Language Model** output when you want to use a MariTalk model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component.📝 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.
| Use the **Language Model** output when you want to use a MariTalk model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. | |
| Use the **Language Model** output when you want to use a MariTalk model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component. |
🤖 Prompt for AI Agents
In docs/docs/Components/bundles-maritalk.mdx around line 21, the word
"component" appears twice in that sentence and needs to be capitalized per the
style guide; update both instances to "Component" (so "Agent" or "Smart
Transform Component") and confirm capitalization matches surrounding headings
and style conventions.
| It can output either a **Model Response** ([`Message`](/data-types#message)) or a **Language Model** ([`LanguageModel`](/data-types#languagemodel)). | ||
|
|
||
| Use the **Language Model** output when you want to use a MistralAI model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Function** component. | ||
| Use the **Language Model** output when you want to use a MistralAI model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Capitalize “Component” per style guide
Please capitalize “Component” to stay aligned with the documentation conventions. As per coding guidelines
-Use the **Language Model** output when you want to use a MistralAI model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component.
+Use the **Language Model** output when you want to use a MistralAI model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component.📝 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.
| Use the **Language Model** output when you want to use a MistralAI model as the LLM for another LLM-driven component, such as an **Agent** or **Smart Transform** component. | |
| Use the **Language Model** output when you want to use a MistralAI model as the LLM for another LLM-driven Component, such as an **Agent** or **Smart Transform** Component. |
🤖 Prompt for AI Agents
docs/docs/Components/bundles-mistralai.mdx around line 21: capitalize the word
“component” to “Component” in the sentence so it reads “Use the **Language
Model** output when you want to use a MistralAI model as the LLM for another
LLM-driven Component, such as an **Agent** or **Smart Transform** Component.”
Ensure both occurrences are updated to match the documentation style guide.
| It only serves as a convenient way for you to view the final output in the **Playground**, rather than inspecting the component logs. | ||
|
|
||
|  | ||
|  |
There was a problem hiding this comment.
Fix typo in DataFrame Operations example alt text.
The alt text currently reads “and the processes it,” which should be “and then processes it” (or similar) to keep the sentence grammatical.
Apply this diff to correct the typo:
-
+📝 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.
|  | |
|  |
🤖 Prompt for AI Agents
In docs/docs/Components/components-processing.mdx around line 205, the image alt
text contains a typo "and the processes it"; update the alt text to "and then
processes it" (or equivalent grammatical correction) so the sentence reads
"...extracts it to a DataFrame with a Smart Transform component, and then
processes it through a DataFrame Operations component."
aimurphy
left a comment
aimurphy
left a comment
There was a problem hiding this comment.
Approving docs changes only. One suggestion got dropped when the new PR was created.
| ## Smart Transform | ||
|
|
||
| In Langflow version 1.5, this component was renamed from **Lambda Filter** to **Smart Function**. | ||
| In Langflow version 1.5, this component was renamed from **Lambda Filter** to **Smart Transform**. |
There was a problem hiding this comment.
| In Langflow version 1.5, this component was renamed from **Lambda Filter** to **Smart Transform**. | |
| In Langflow version 1.5 and 1.6, this component was renamed. | |
| It's previous names include **Lamba Filter** and **Smart Function**. |
This comment has been minimized.
This comment has been minimized.
Codecov Report✅ All modified and coverable lines are covered by tests. ❌ Your project status has failed because the head coverage (46.59%) is below the target coverage (55.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## main #10003 +/- ##
==========================================
- Coverage 23.97% 23.72% -0.25%
==========================================
Files 1091 1091
Lines 40014 39993 -21
Branches 5543 5531 -12
==========================================
- Hits 9594 9489 -105
- Misses 30249 30333 +84
Partials 171 171
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
github-actions
Bot
added
bug
This comment has been minimized.
This comment has been minimized.
|
|
Build successful! ✅ |
3 participants
FIX
This pull request updates the documentation for all supported language model components to use consistent terminology. Specifically, it replaces references to "Smart Function" components with "Smart Transform" components when describing how to connect language model outputs to other LLM-driven components. This improves clarity and ensures alignment with current component naming conventions.
Documentation terminology updates:
LanguageModeloutput in a flow. This affects documentation for AI/ML API, Amazon Bedrock, Anthropic, Azure OpenAI, Baidu Qianfan, Cohere, DeepSeek, Groq, Hugging Face, IBM watsonx.ai, LM Studio, MariTalk, MistralAI, Novita, Ollama, OpenAI, OpenRouter, Perplexity, SambaNova, and Vertex AI components. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]Summary by CodeRabbit
Documentation
Style