feat: standardize placeholder text for exchange API credentials#536
Merged
Conversation
standardize placeholder text for exchange API credentials
standardize placeholder text for exchange API credentials
su8su
approved these changes
Dec 5, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
standardize placeholder text for exchange API credentials
📝 Pull Request Template
1. Related Issue
Closes # (issue number)
2. Type of Change (select one)
New Feature
3. Description
This PR improves the user experience by standardizing the placeholder text for API Key, Secret Key, and Passphrase inputs across various exchanges (Binance, OKX, Hyperliquid, etc.).
4. Testing
5. Checklist