Bump go.bbkane.com/warg from 0.0.23 to 0.0.26

[dependabot]

Bumps go.bbkane.com/warg from 0.0.23 to 0.0.26.

Changelog

Sourced from go.bbkane.com/warg's changelog.

v0.0.26

Changed

• Moved SetBy into the Value interface (value.UpdatedBy() - this allows Flag to be readonly and and makes the coupling between setting the value and updating UpdatedBy explicit
• Flags must now be the last things passed - i.e. <appname> <section> <command> <flag>.... In addition, the only flag allowed after a <section> is the --help flag (unfortunately the --color flag is NOT currently allowed to be passed for section help). This simplifies the parsing and will help with tab completion, and after that's implemented I might try to restore the old behavior if I get too annoyed with this limitation. Temporarily, the old behavior can be restored by setting the WARG_PRE_V0_0_26_PARSE_ALGORITHM environment variable, but I plan to remove that in the next version.

Examples:

$ go run ./examples/butler --color false -h
Parse err: Parse args error: expecting section or command, got --color
exit status 64

$ WARG_PRE_V0_0_26_PARSE_ALGORITHM=1 go run ./examples/butler --color false -h
A virtual assistant
# ... more text ...

v0.0.25

Added

• path.Path type that users should call Expand/MustExpand on. See Removed

Changed

• The signature of value.EmptyConstructor no longer has the opportunity to return an error. I don't think anything ever returned an error, so this was never needed.

Removed

• Removed value.FromInstance. This is a nasty silent breaking change because it'll break users at runtime (not compile time) when they update warg. However, value.FromInstance was only used for expanding ~ in Path's from default values - no other value types needed it. It also wasn't really testable since the value ~ expanded to is different per machine (without env var shennanigans). I'm replacing it with a Path type that the

... (truncated)

Commits

• 305b9fc Merge pull request #81 from bbkane/bbkane/parse2
• 0c09c43 Update CHANGELOG, WARG_PRE_V0_0_26_PARSE_ALGORITHM
• 24080f1 Clearer error messages
• cc48ea9 Test for passing flag before command
• 2b737fa Test for passing a bad section/command name
• 67ac494 Validation error on command/section name clash
• 781b4eb Allow help flag alias when parsing
• e23b27f Add UnsetSentinel support
• d1f0223 Move scalar value update check inside scalar impl
• 0941dbb Error if scalar flag is passed twice
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Looks like go.bbkane.com/warg is up-to-date now, so this is no longer needed.