This repository was archived by the owner on Jul 22, 2025. It is now read-only.
FIX: forced tools wasn't set correctly when tool has no options. #1231
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
romanrizzi
force-pushed
the
fix-forced-tools
branch
from
9beca96 to
ced39d1
Compare
romanrizzi
force-pushed
the
fix-forced-tools
branch
from
ced39d1 to
ad0d8e8
Compare
romanrizzi
changed the title
nattsw
approved these changes
Mar 31, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Forcing a tool without options was sent to the server as:
["ListCategories", undefined, true]which was stored as:
["ListCategories", true, false]because how the controller handles the params.