Improve the user input prompt string #541
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
sfrieds3
requested review from
gorillamoe,
Grueslayer and
YaroSpace
as code owners
YaroSpace
previously approved these changes
May 17, 2025
|
Nice! Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Improves the user input prompt string when using
# @prompt some-variable.Currently, the variable name appears after the prompt string and a colon, without spacing before the user input. This change moves the variable name into brackets before the colon, making the prompt clearer.
Before:
Enter value for variable: some-variable<cursor>After:
Enter value for variable [some-variable]: <cursor>