-
Notifications
You must be signed in to change notification settings - Fork 2.7k
fix: Refactor API Key Inputs to Use PasswordInputField Component #8639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Replaced VSCodeTextField with PasswordInputField for API key inputs across multiple provider components (Bedrock, Cerebras, Chutes, DeepInfra, DeepSeek, Doubao, Featherless, Fireworks, Gemini, Glama, Groq, HuggingFace, IOIntelligence, LiteLLM, Mistral, Moonshot, Ollama, OpenAI, OpenAICompatible, OpenRouter, Requesty, SambaNova, Unbound, VercelAiGateway, XAI, ZAi). - Introduced a new PasswordInputField component to handle password visibility toggling and improved accessibility. - Updated imports and adjusted props accordingly to maintain functionality and styling.
|
Fix confirmed. Works. Ready for review. |
|
Looks good UX-wise 👍 |
Review Complete ✅No new issues found in this review. The merge from main (commit 0ceaf9d) brings the PR branch up to date with comprehensive tool protocol resolution improvements and other updates. The previously resolved API callback signature issue in
Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues. |
Replace instances of VSCodeTextField with a new PasswordInputField component for API key inputs across multiple provider components, enhancing password visibility toggling and accessibility. Remove unused imports related to VSCodeTextField.
Fixes #8638