.Net: Expose GeminiKernelFunctionMetadataExtensions #12515
+8
−43
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
GeminiToolCallBehavior
exposes the methodEnableFunctions
to enable filtering which Kernel Functions are available for auto invoke. However, there's no way to construct aGeminiFunction
instance since the constructor is internal.I saw there's an extension to build a
GeminiFunction
from aKernelFunctionMetadata
, but it's under the test project. It seems that it was supposed to be exposed from the library, since there's also a test file forKernelFunctionMetadata
.This way, it will be possible to use
GeminiToolCallBehavior.EnableFunctions
to explicitly specify which tools can be auto-called by the Google connector.Description
SemanticKernel.Connectors.Google.UnitTests
toMicrosoft.SemanticKernel.Connectors.Google.Extensions
namespace.FunctionMetadataAsGeminiFunction
and start usingGeminiKernelFunctionMetadataExtensions
instead.Contribution Checklist