fix: Handle object-type API key in OpenAI Moderation embed

[rahulb18]

Fixes #4663

When OpenAI Moderation is used in embedded chat, the API key was being passed as an object instead of a string, causing a 401 error with "[object Object]" being sent to OpenAI's API.

Changes:

• Updated OpenAIModerationRunner constructor to handle both string and object type API keys
• Added type checking to extract the API key from object properties (openAIApiKey, apiKey, or key)
• Maintains backward compatibility with string-type API keys

This fix ensures moderation works correctly in both internal chat canvas and embedded chat contexts.

[gemini-code-assist]

Summary of Changes

Hello @rahulb18, I'm Gemini Code Assist¹! 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 resolves an issue where OpenAI Moderation failed in embedded chat due to the API key being passed as an object instead of a string. The core change involves enhancing the OpenAIModerationRunner to intelligently handle both string and object formats for the API key, ensuring robust moderation functionality across all integration points.

Highlights

• API Key Handling: The OpenAIModerationRunner constructor has been updated to correctly process API keys, whether they are provided as a string or an object.
• Object-type API Key Extraction: New type-checking logic was added to extract the actual API key from common object properties like openAIApiKey, apiKey, or key when an object is passed.
• Backward Compatibility: The changes ensure that existing string-type API key configurations continue to function without issues.
• Bug Fix: This resolves a 401 error that occurred when OpenAI Moderation was used in embedded chat, where the API key was incorrectly passed as an object.

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 👍 and 👎 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.

Footnotes

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. ↩

[gemini-code-assist]

Code Review

This pull request addresses a bug where the OpenAI API key was being passed as an object in embedded chats, leading to authentication errors. The fix in OpenAIModerationRunner.ts is well-targeted, adding logic to handle an object-based API key by extracting it from a set of possible properties. This ensures moderation works correctly in different contexts while maintaining backward compatibility.

I've provided a couple of suggestions to improve type safety and code clarity in the constructor. One is a minor tweak to the type signature, and the others address a potential type safety issue in the key extraction logic to prevent potential runtime errors from non-string key values.