feat: add short flag aliases via FlagMetadata.Short#11
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds support for single-character short flag aliases (e.g.,
-vfor--verbose) driven by the existingFlagMetadatastruct.A new
Shortfield onFlagMetadataregisters the short alias in the combined flag set sharing the sameValuepointer as the long flag, so all four input forms (-v,--v,-verbose,--verbose) work out of the box via Go'sflagpackage.The help output uses conventional formatting:
-v, --verbosefor flags with a short alias, and--config(padded) for flags without one when any sibling has a short alias. Flags without any short aliases in the set skip the padding entirely. The display also now uses double-dash (--) for long flag names to match CLI conventions.Fix #1