.Net: Add responseMimeType Parameter to GeminiPromptExecutionSettings for Enhanced Output Control. #9870
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
Why is this change required?
The absence of the
responseMimeType
property in .NET prevented users from leveraging structured output formats available in the Gemini API, causing unintended behavior in scenarios requiring JSON or controlled output.What problem does it solve?
Adds flexibility for developers by enabling control over MIME type responses, particularly for JSON data parsing and classification tasks.
What scenario does it contribute to?
responseMimeType
support.Fixes #9863
Description
This PR adds support for the optional
responseMimeType
parameter to theGeminiPromptExecutionSettings
class, allowing for better control over the output response format in Gemini API calls. This change addresses the missing ability to specify MIME types for valid JSON, plain text, or enumerated outputs.Contribution Checklist