Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tool.from_tool()previously required aToolobject as its first argument, but the@tooldecorator (since v3.0) returns the original function with metadata attached rather than aToolobject. This meant the documented workflow of decorating a function and then transforming it before registration would crash withAttributeError: 'function' object has no attribute 'parameters'.Now
from_toolaccepts either aToolor a callable, auto-coercing the latter viaTool._ensure_tool(). This respects any@tooldecorator metadata (name, description, etc.) on the function, so the documented pattern works naturally:The coercion reuses
FunctionTool.from_function(fn, metadata=meta)rather than expanding kwargs, keeping it in sync with the existing metadata path.Closes #3232