Releases: integrii/flaggy
Releases · integrii/flaggy
v1.8.0
v1.7.1
v1.7.0
This is a follow up v1.7.0 release after rapid re-release of v1.6.0 tag caused go module caching error. This release addresses nearly all known issues and proposed feature additions of Flaggy while retaining a no-dependency policy.
- Update module to Go 1.25
- Streamline argument delegation between parsers
- Clarify benchmark intent and document agent workflow
- Fixes #68 - Subcommands and globals are displayed in different help sections on subcommands
- Refactored help output logic
- Fixes #96 - Empty flag causes missing input error
- Added Fixes #74 improved alignment on help output
- Add benchmark tests
- New gopher logo on README.md
- Fixes #98 - add CONTRIBUTING.md
v1.6.0
🎉 First release since May 2022 thanks to AI! 🎉
Disruptive Changes:
- Slice flags no longer automatically parse slice values with commas into multiple values. To specify multiple values, use the flag multiple times. For example, this will produce one value:
./app -f one,two,threeand./ -f one -f two -f threewill produce three values in the slice. #90
New Features:
- Adds built-in bash and zsh completion generators. Use
completion zshorcompletion bashon your app. This is on my default. To disable, useflaggy.DisableCompletion(). #1 - Flags can now be sorted alphabetically or reverse alphabetically using
SortFlagsByLongName()andSortFlagsByLongNameReversed()#69 - Added a Github Action for test validation
- Added support for all types in the go standard library!
• []net.IPMask
• time.Time
• url.URL
• net.IPNet
• net.TCPAddr
• net.UDPAddr
• os.FileMode
• regexp.Regexp
• time.Location
• time.Month
• time.Weekday
• big.Int
• big.Rat
• netip.Addr
• netip.Prefix
• netip.AddrPort
• Base64Bytes ([]byte)
Fixes
- Fixed #84 - Unknown arguments supplied when the flag and subcommand have the same value name
Full Changelog: v1.5.2...v1.6.0
v1.5.2
If you would like to use a variable number of arguments at the end of your program without the user specifying -- before the list, you can do this by setting flaggy.ShowHelpOnUnexpectedDisable() and then parsing the []string at flaggy.TrailingArguments. For more details, see Issue #79
- new trailingArguments example
- new tests for trailing arguments with positionals. fixed trailing arguments being incorrectly considered as positionals
v1.5.1
v1.5.0
Important! A build error snuck into this release. Please use v1.5.1!
What's Changed
- Add new
TrailingSubcommand()method to find the last subcommand used by parsers @mattwiller in #75 - cosmetic: simplify Parser by @marco-m in #70
- blackbox test: actually assert something by @marco-m in #73
- Add useful info to AddPositionalValue panic. by @groutr in #77
- Linter fixes by @marco-m in #71
Thank you to our new contributors! 🎉
- @marco-m made their first contribution in #70
- @groutr made their first contribution in #77
- @mattwiller made their first contribution in #75
Full Changelog: v1.4.4...v1.5.0