Skip to content

feat: support path parameters in tools and improve execution strategies#226

Merged
hendrikmennen merged 13 commits into
one-ware:mainfrom
FEntwumS:feature/path-parameter-in-tools
May 18, 2026
Merged

feat: support path parameters in tools and improve execution strategies#226
hendrikmennen merged 13 commits into
one-ware:mainfrom
FEntwumS:feature/path-parameter-in-tools

Conversation

@swittlich
Copy link
Copy Markdown
Contributor

@swittlich swittlich commented May 7, 2026

This PR introduces support for Path Parameters within the Tool Engine. This allows for more robust handling of file system paths when invoking external tools, ensuring platform-specific path resolution and validation.

Key Changes

  • Tool Engine Enhancements: Added support for path-based parameters in tool configurations.
  • ToolCommandBuilder: Refactored the command builder to handle path resolution dynamically.
  • Execution Strategy: Implemented a fallback mechanism to NativeStrategy for tool execution.
  • Interfaces: Expanded IProject and tool-related interfaces (e.g., adding StartWeakProcess) to support the new workflow.

Technical Details

  • Fixed platform-specific test failures in the ToolEngine that occurred during CI.
  • Cleaned up the ToolCommandBuilder architecture to separate argument parsing from path resolution.

Testing

  • Added a new suite of unit tests for ToolCommandBuilder.
  • Verified path resolution across different OS environments (Linux/Windows).

@swittlich swittlich changed the title Showcase impl feat: support path parameters in tools and improve execution strategies May 12, 2026
@swittlich swittlich requested a review from hendrikmennen May 12, 2026 11:35
@swittlich swittlich marked this pull request as ready for review May 12, 2026 11:35
@hendrikmennen hendrikmennen merged commit a38b2c0 into one-ware:main May 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants