feat: update authentication ui

[allen-stephen]

Description

Update authentication UI to provide common auth methods in an easy-to-use dropdown.

Features:

• Auth method dropdown (No Auth, Basic Auth, Bearer Token, API Key)
• Dynamic form inputs based on selected auth method
• Automatic header generation for each auth type
• Custom headers always available alongside any auth method
• Full light and dark mode support

[gemini-code-assist]

Summary of Changes

Hello @allen-stephen, 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 significantly enhances the user interface for handling HTTP authentication and headers. It provides a streamlined and intuitive way for users to configure common authentication methods like Basic Auth, Bearer Tokens, and API Keys through a new dropdown and dynamic input fields. This change improves usability by automating the generation of authentication headers and clearly separating custom headers, making it easier to manage request configurations.

Highlights

• New Authentication UI: Introduced a dropdown for selecting common authentication methods: No Auth, Basic Auth, Bearer Token, and API Key.
• Dynamic Input Fields: Input fields for authentication details (e.g., token, username/password, API key/header name) are dynamically rendered based on the selected authentication type.
• Automatic Header Generation: The application now automatically constructs and includes the correct Authorization or custom API key headers based on the user's authentication input.
• Integrated Custom Headers: Custom headers can still be added and are applied alongside any chosen authentication method, ensuring flexibility.
• UI/UX Enhancements: Updated styling for various UI elements, including headers and collapsible sections, to accommodate the new authentication features and improve overall aesthetics, with full light and dark mode support.

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 introduces a new authentication UI, which is a great enhancement. The changes include a dropdown for selecting auth methods and dynamic input fields. My review includes a high-severity recommendation to refactor the dynamic HTML generation to use DOM APIs instead of innerHTML. This will improve security by preventing potential XSS vulnerabilities and also fix a bug with unescaped attribute values. I've also pointed out an unused variable that can be removed. The overall implementation is solid and the new feature is well-executed.

[dmandar]

Pls add tests