feat: Tool Mode Support for File Components

[erichare]

This pull request introduces enhancements to file input handling by adding support for "tool mode" in various components. The primary focus is to enable or improve tool mode functionality for file-related inputs, which likely affects how these inputs are processed or displayed in tool integrations.

File Input Enhancements:

• Added the ToolModeMixin to the FileInput class, enabling tool mode capabilities for file inputs.
• Set tool_mode=True for the file input in base_file.py to ensure compatibility with tool mode operations.
• Enabled tool_mode for the file_name input in the SaveToFileComponent, allowing this input to function correctly in tool mode contexts.

Summary by CodeRabbit

• New Features

  • Enabled tool-mode behavior for file inputs, including path and file name fields, improving consistency and flexibility in the UI.

• Chores

  • Updated Google dependency to version 1.117.0.
  • Refreshed starter project metadata.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

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

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

Walkthrough

Adds tool-mode support to file-related inputs by mixing ToolModeMixin into FileInput and enabling tool_mode on specific inputs in BaseFileComponent and SaveToFileComponent. Updates a starter project JSON’s metadata and a dependency version.

Changes

Cohort / File(s)	Summary
Tool-mode enablement for file inputs src/lfx/src/lfx/base/data/base_file.py, src/lfx/src/lfx/components/data/save_file.py, src/lfx/src/lfx/inputs/inputs.py	Add ToolModeMixin to FileInput; set tool_mode=True on BaseFileComponent path input and SaveToFileComponent file_name input.
Starter project metadata update src/backend/base/langflow/initial_setup/starter_projects/News Aggregator.json	Update code_hash and bump google dependency from 0.8.5 to 1.117.0.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User
  participant UI as UI
  participant FileInput as FileInput (ToolMode)
  participant Components as Components (BaseFile/SaveToFile)

  User->>UI: Provide file path / name
  UI->>FileInput: Set values (tool_mode)
  Note over FileInput: Tool-mode metadata available
  FileInput->>Components: Deliver input (path/file_name)
  Components-->>User: Perform read/save using provided inputs

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• feat: Better multi-file consistency for File Component #8625: Also modifies FileInput/base inputs for dynamic behavior, overlapping with tool-related input configuration.
• refactor(setup): generalize tool/agent node logic and update starter templates #8618: Updates tool/agent detection and templates tied to tool_mode, related to enabling tool_mode on inputs.

Suggested labels

python, size:S, lgtm

Suggested reviewers

• ogabrielluiz
• rodrigosnader
• edwinjosechittilappilly

Pre-merge checks and finishing touches

❌ Failed checks (1 error, 2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Test Coverage For New Implementations	❌ Error	The pull request adds ToolModeMixin to FileInput and sets tool_mode=True in BaseFileComponent and SaveToFileComponent but the raw summary and changed file listing include only source files under src and no new or updated test files (neither backend test_*.py nor frontend *.test.ts/js). Because this implements a new feature, corresponding unit or integration tests covering the new tool_mode behavior are required but absent.	Please include backend unit tests (named test_*.py) that verify FileInput’s ToolModeMixin integration and that BaseFileComponent and SaveToFileComponent correctly honor tool_mode=True, and add at least one integration test simulating a tool-mode file operation to validate end-to-end behavior.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Test Quality And Coverage	⚠️ Warning	The changes introduce tool_mode support in the FileInput class, BaseFileComponent, and SaveToFileComponent, but existing tests do not validate this new behavior: FileInput’s inheritance change is not directly tested for the presence or behavior of the tool_mode attribute, BaseFileComponent’s addition of tool_mode=True on its path input is unverified in its unit tests, and the SaveToFileComponent tests are currently marked as skipped and hence do not cover the updated tool_mode flag.	Add targeted pytest unit tests that assert FileInput instances include and default the tool_mode attribute, extend the BaseFileComponent tests to verify that its file input is configured with tool_mode=True, and re-enable or add new tests for SaveToFileComponent to confirm its file_name input sets tool_mode correctly.
Test File Naming And Structure	❓ Inconclusive	I attempted to verify that the tests covering these file/tool-mode changes follow the required naming and structure, but this pull request only adjusts component code and does not include any accompanying test updates. Without access to the existing repository test suite from this environment (GitHub code search requires authentication), I cannot confirm whether current tests satisfy the specified patterns or cover the new tool-mode behavior. Therefore I cannot complete the requested verification.	Please review the relevant backend, frontend, and integration tests to ensure they follow the prescribed naming conventions, include descriptive pytest/Playwright structures, and cover both positive and negative tool-mode scenarios introduced in this change, then share the findings so the check can be completed.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly and accurately conveys the main change—adding tool mode support to file-related components—using clear terminology without extraneous details, making it easy for team members to understand the purpose at a glance.
Excessive Mock Usage Warning	✅ Passed	This pull request does not introduce or modify any test files, and all changes are confined to production code for file input components and their configuration. Since there are no new or altered tests in this PR, there is no scope for excessive mock usage to occur here, and the existing test suite remains unchanged. Therefore, the check for excessive mock usage in tests does not apply to these changes and passes without issue.

---

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

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 23.67%. Comparing base (75e2650) to head (267baa1).
⚠️ Report is 32 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10049      +/-   ##
==========================================
- Coverage   23.68%   23.67%   -0.01%     
==========================================
  Files        1090     1090              
  Lines       39768    39765       -3     
  Branches     5542     5542              
==========================================
- Hits         9419     9416       -3     
  Misses      30178    30178              
  Partials      171      171              

Flag	Coverage Δ
backend	46.19% <ø> (ø)

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

🚀 New features to boost your workflow:

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

[erichare]

@ogabrielluiz this is a small (well small in code, possibly larger in implications). The ask was for a tool mode on both Read File and Write File - for Read, this appears to require a ToolModeMixin on FileInput. Otherwise, i just added the appropriate tool mode booleans for the relevant inputs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud