-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor tool function calling code #193
Refactor tool function calling code #193
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would feel better about this refactoring if we first had a robust set of tests around calling action functions and conversions using the current implementation before we move the code (and its corresponding, but not established) tests,
Ok, I can write tests for the existing implementation and then use them here to verify these changes |
e44200f
to
722bd10
Compare
Rebased to include the tests from PR #201 and updated tests for the relocated functions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small comments, but overall LGTM
Co-authored-by: Steffen Zschaler <[email protected]>
…rather than lookup via ActionFunction class.
Long awaited changes for #40 refactor tool function calling code. Mostly moving tool function and conversion function invocation to
ToolsManager
andFunctionRegistry
.There is still moving the
getActionFunction()
fromToolsManager
intoFunctionRegistry
todo but raised as issue #192 because it requires some rework ofFunctionRegistry