-
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 function calling code by moving it into ToolManager or FunctionRegistry #40
Comments
barnettwilliam
added a commit
that referenced
this issue
May 5, 2023
… following the naming of: invokeActionFunction, resolve, convert, find, call. Added wrapper functions for functionality that will be relocated as part of issue #40.
barnettwilliam
added a commit
that referenced
this issue
Mar 12, 2024
…er and FunctionRegistry as part of #40
This was referenced Mar 12, 2024
barnettwilliam
added a commit
that referenced
this issue
Mar 22, 2024
…er and FunctionRegistry as part of #40
barnettwilliam
added a commit
to mdenet/educationplatform-docker
that referenced
this issue
Mar 26, 2024
…refactor action function calling, mdenet/educationplatform#190 tests for ActivityValidator, mdenet/educationplatform#201 tests for EducationPlatformApp action function calling, mdenet/educationplatform#200 populate only required tool function parameters, mdenet/educationplatform#198 tests for EducationPlatformApp, and mdenet/platformtools#66 changed OCL tool language type to text.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is about moving the code for calling action functions (and probably for conversion of parameters) into
ToolManager
or even into theFunctionRegistry
.This depends on the refactoring in #34 being completed first, so that there actually is a function to move.
The text was updated successfully, but these errors were encountered: