feat(toolbox-llamaindex)!: Base toolbox-llamaindex over toolbox-core #244
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.
Similar to #229 but for
toolbox-llamaindex
.This PR introduces a new dependency on the foundational library
toolbox-core
.Breaking Changes
This PR introduces changes to how "strictness" is handled across several toolbox functions. The
strict
flag has been removed fromload_tool
,aload_tool
,add_auth_token_getter(s)
, andbind_param(s)
. Additionally, the default behavior ofload_toolset
forstrict=False
has changed.Why?
Enforces more explicit error handling and reduce ambiguity, particularly in scenarios where unused configurations might otherwise be silently ignored.
*
(a)load_tool
do not supportstrict
flag now:Before
After
*
(a)load_toolset
functionality changes forstrict=False
Before
Does not throw error if none of the loaded tools use a given auth token getter or bound param. Only throws a warning.
After
Throws error if none of the loaded tools use a given auth token getter or bound param.
*
add_auth_token_getter(s)
do not supportstrict
flagBefore
After
*
bind_param(s)
do not supportstrict
flagBefore
After