This repository was archived by the owner on Mar 6, 2025. It is now read-only.
Pre-populate username #185
Merged
Conversation
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
If a username is set, charm now pre-populates the input field with it in the "set username" section. Resolves charmbracelet#16
|
I'm open to addressing the remaining bits in #17 (comment) regarding moving the lookup into |
aymanbagabas
approved these changes
Feb 21, 2023
|
Thank you so much for the contribution! I removed the parameter for setting a placeholder as it wasn't really necessary. It now defaults to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If a username is set, charm now pre-populates the input field with it in the "set username" section. Resolves #16.
I tried to incorporate some of the feedback given in #17 (comment) but I'm new to bubble tea.