.Net: Allow strings to be passed for int arguments in TextSearch KernelFunctions #10147
+24
−2
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.
Motivation and Context
The
GetArgumentValue
method that is called as part of creating KernelFunctions for TextSearch inTestSearchExtensions
requires that arguments be passed as integers for "count" and "skip". While using this functionality with a gpt-4o model through Azure OpenAI, the function calls were given arguments that had values encoded as strings. This caused the default count of 2 to always be used, no matter what the LLM was calling for. I noticed this behavior even if I explicitly set the ParameteryType of the KernelParameterMetadata to be int.Description
This changes the
GetArgumentValue
method inTextSearchExtensions
to allow for integers passed as string values. This will avoid the confusing behavior of the arguments being ignored for TextSearch plugins.Contribution Checklist