Fix Microsoft.Extensions.AI wrapper encoding of inline data when mapping to DataContent
Microsoft.Extensions.AI wrapper double-encoded inline data when mapping to DataContent.
Summary of Changes
Hello @PederHP, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request addresses a critical bug in the Microsoft.Extensions.AI wrapper that caused inline data to be incorrectly double-encoded when being processed and mapped to DataContent. By changing the data conversion method from a UTF-8 byte conversion to a Base64 string decoding, the PR ensures that inline data is handled correctly, preventing data corruption and maintaining the integrity of content within the AI wrapper.
Highlights
- Data Encoding Fix: Resolved an issue where inline data within the Microsoft.Extensions.AI wrapper was being double-encoded when mapped to
DataContent. - Decoding Mechanism Update: The conversion for
InlineDatahas been updated fromEncoding.UTF8.GetBytestoConvert.FromBase64String, ensuring proper decoding of Base64-encoded data. - Code Formatting: A minor formatting adjustment was made to remove an unnecessary newline character at the end of the
AbstractionMapper.csfile.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in pull request comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
[^1]: Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.
Hi @PederHP
Another great catch. Thanks. It's currently conflicting with the current code base from another PR which I'm going to resolve.
Cheers