Repository navigation
Releases
v0.11.0
CONGA v0.11.0 makes completion follow each field's declaration more closely: an enum narrows the field's predictor, map values complete from their value type, and a type's Predict runs only when the shell completes that field. Programs that declare enum on path fields now fail at startup.
🚀 Highlights
enumnarrows completion: A field with anenumtag offers only theenumvalues, drawn from its predictor so they keep their descriptions and order.system.Signalwithenum:"TERM,INT,HUP"now offers three signals instead of every spelling of every signal. The newpredict.Predictor.Includeexposes the same filter to predictor authors (#218, closes #128).- Map values complete: Map flags and positionals complete the value after
key=from the value type's predictor, somap[string]*time.Locationwithtimezone.RegisterLocationoffers time zones aftereu=. A map withouthelpnames its value type in the hint, such as<key>=<Path to a file>(#223, closes #217). Predictruns only when needed: With completion enabled, ordinary runs,--helpand--whyno longer call every type'sPredict. A completion request calls it only for the field being completed (#222, closes #129).
⚠ Breaking Changes & Migration
enumon path fields fails at startup (#221): Schema build rejectsenumwithErrSchemaonconga.File,conga.Dir,conga.FileContent(including slices and pointers of them), on types implementingpredict.FileFilterable,DirFilterableorPathFilterable, and on fields with afile,dir,execorsymlinkpredictor. Removeenum, useglobonconga.File, or use a string field withenumand no path predictor.conga-lintreports the same error.
✨ Features
- completion: Add
predict.Predictor.Include(values ...string), and narrow a field's predictor to itsenumvalues (#218). - completion: Complete map values from their value type. Entries split at the first
=as the run does,predictor:"file"(ordir,exec,symlink) on a map completes the value afterkey=, and slice and map element predictors keep a timeout raised withTimeout(d)(#223).
🐛 Bug Fixes
- completion: Call a type's
Predictonly when completing that field. In programs with completion enabled, a panickingPredictnow fails only that field's completion request (exit 2) instead of crashing every run (#222). - completion: Slice completion keeps
envs/dev.yamlafterdev.yamlwas given.predict.Predictor.ExcludeandRawnow compare each candidate'sValueafterPrefixandSuffix, neverDisplay; on aMultiPartspredictor, callExcludeon the predictor the segment function returns (#218). - completion: Finished segmented values such as
--image api-gateway:v3.2.0and later list elements get a trailing space, andTimeoutalternatives keep their own modifiers (#218). - lint: Report the map tag rules (no
enum,rangeorlenon a map, string keys only) as the program does, stop reporting domain tags such asexisting:"true"onOptionalFlag[*conga.File]as unknown, and reportrangeon a map with the program's message (#221).
Full Changelog: v0.10.0...v0.11.0
Requirements: Go 1.27+ · Docs · pkg.go.dev
v0.10.0
CONGA v0.10.0 simplifies typed map binding—eliminating App.RegisterMap—and tightens startup validation across map types, config environment variables, boolean struct tags, and conga-lint diagnostics.
🚀 Highlights
- Zero-registration typed maps: Typed maps now bind automatically without
App.RegisterMapand parse keys and values through registeredTypeParsers, including maps keyed or valued by named string types. Slice- and map-kind types with their own text unmarshaler, such asnet.IP, bind as one value, and a missing parser fails at startup (#210, #215). - Safer config-variable reservation: Apps reserve
<PREFIX>_CONFIGonly when they register a config decoder or declare aConfigFilefield, and both runtime schema build andconga-lintcatch flags or features bound to that variable at startup (#214, #216). - Strict boolean tags & unified schema diagnostics:
hidden,negatable, andbootstrapreject misspelled tag values at startup (#212), andconga-lintshares exact schema error formatting with the runtime (#211).
⚠ Breaking Changes & Migration
API changes
App.RegisterMapremoved;RegisterTyperejects slices and maps (#210, closes #121, #113):- Delete
app.RegisterMap(...)calls—typed maps now bind automatically. - Move any predictor previously passed to
RegisterMaponto apredictor:"<name>"struct tag paired withapp.Predictor("<name>", p), or implement aPredictmethod on a named map type. App.RegisterTypenow panics for slice and map types; register aTypeParserfor the element or value type instead.
- Delete
Schema & startup guards
- Config environment variable collisions (#214, closes #168):
- In apps that read a config variable (via a registered decoder or a
ConfigFilefield), any flag or feature bound to that variable (such as aConfigflag underEnvPrefix) now fails at startup withErrSchema. Give it an explicitenv:"..."tag or opt out withenv:"-".
- In apps that read a config variable (via a registered decoder or a
- Unparseable field types fail at startup (#210):
- Any flag or positional argument whose type, slice element, or map key/value has no parser now fails schema build with
ErrSchemainstead of failing later when a user supplies a value.
- Any flag or positional argument whose type, slice element, or map key/value has no parser now fails schema build with
- Strict boolean struct tags (#212, closes #165):
hidden,negatable, andbootstrapvalues other than empty,"true", or"false"(such as"yes","1", or"True") now fail at startup withErrSchema. Use the bare tag,"true", or"false".
Configuration
- Config environment variable only for config-capable apps (#214, closes #168):
- Apps without a decoder or
ConfigFilefield no longer read<PREFIX>_CONFIG, andenv:"-"onConfigFilenow disables its environment variable.
- Apps without a decoder or
Errors & diagnostics
- Unified schema and
conga-linterror wording (#211, closes #126):- Shadowing errors end in
"on an ancestor command"without the command name. - Missing-
Runnererrors read:struct <Name>: schema error: runner not implemented: implement conga.Runner: Run(context.Context, *conga.Session) error. - Duplicate
ConfigFileerrors read:duplicate ConfigFile field (already declared by field <First>). - Update callers or tests that assert the previous message text.
- Shadowing errors end in
🐛 Bug Fixes
- maps: Bind maps keyed or valued by named string types without panicking in
reflect.Value.Convert(#215). - lint: Report flags, features, and
Featuresmap variables bound to the reserved config-file environment variable, matching runtime schema build (#216).
📚 Documentation
- struct-tags: Clarify that the
lentag measures rune count on strings and applies per element on slices, while maps useitemsand rejectlenat schema build (#213, refs #166).
Full Changelog: v0.9.0...v0.10.0
Requirements: Go 1.27+ · Docs · pkg.go.dev
v0.9.0
CONGA v0.9.0 is a broad reliability release covering strict configuration key matching, source-aware error classification, stricter flag and input parsing, and cross-shell completion fixes.
🚀 Highlights
- Exact config key matching & casing options: Configuration files match keys strictly by
configtag or flag name, withconga.ConfigKeyCase(KebabCase,SnakeCase,CamelCase) for app-wide casing (#183). - Source-aware error classification: Environment-, config-, and default-sourced value and group failures now classify consistently under
ErrConfig(exit 1, no usage block) instead of usage errors (exit 2) (#190, #192, #205). - Stricter parsing & safer executables:
Counterrejects=Non the CLI, empty boolean values fail cleanly, repeated stdin reads are caught before coercion, and./toolexecutables resolve in the working directory rather than$PATH(#186, #187, #193, #203). - Cross-shell completion &
LS_COLORS: Multibyte cursor handling, quote/escape handling across Bash/Zsh/Fish/PowerShell/Nushell,keepordersupport, andLS_COLORSSGR styling (#198, #199, #201).
⚠ Breaking Changes & Migration
Schema & startup guards
- Built-in and
Featuresflag collisions (#189, closes #148):- An ancestor
--jsonflag with a mountedVersionCommand, or an ancestor flag colliding with a CLI-exposedFeaturesflag, now fails schema build withErrSchema. Rename the ancestor flag or rely on--version.
- An ancestor
featureonimplicit:"true"commands (#194, closes #160, #161):- Declaring a
featuretag on animplicit:"true"command fails schema build withErrSchema; gate the parent command or make the subcommand explicit.
- Declaring a
bootstraponFileContent(#187):bootstrap:"true"on aFileContentfield now fails schema build withErrSchema; useconga.Fileand read it inBootstrap.
Configuration
- Exact config keys and nested sections (#183, closes #142, #143, #182):
- Config keys must match the flag name or
configtag exactly (api_endpointno longer binds--api-endpointby default and fails withErrConfig, exit 1). Update your config file, setconga.ConfigKeyCase(conga.SnakeCase), or addconfig:"<key>". - Flag/subcommand aliases no longer work as config keys, dotted
configtags map only to nested sections, and flags with an explicitconfigtag no longer fall back to their flag name.
- Config keys must match the flag name or
<PREFIX>_CONFIGoutranksconga.ConfigExplicit(#135, closes #117):- Config targets now resolve in order:
--config-file><PREFIX>_CONFIG>ConfigExplicit(path)> search paths. When<PREFIX>_CONFIGis set, a missingConfigExplicitfile is no longer read or errored on.
- Config targets now resolve in order:
- Stricter HCL, JSON, and YAML decoding (#184, closes #145, #146):
- HCL labeled blocks and attribute/block name collisions fail to load instead of being dropped.
- Integers outside the
int64anduint64ranges fail to load in JSON, YAML, and HCL withErrConfig(exit 1), and the cause matches the decoder's ownErrParse(for examplejson.ErrParse). JSON and HCL also reject numbers that overflowfloat64.
.envescaped dollars (#195, closes #159):\$inside a double-quoted.envvalue is now a literal$instead of starting variable expansion.
Command-line behaviour
- Strict
Counterflags (#186, closes #149):Counterrejects attached CLI values (--verbose=2,-v=2); repeat the flag (-vv), set via env/config, or useOptionalFlag[int].- Negative and signed counts from env/config are rejected, and counter errors now say
"unsigned integer".
- Empty booleans rejected (#193, closes #171):
--flag=, emptymap[string]boolvalues, and empty boolean config strings no longer meantrue. Pass--flagor--flag=true.
FileContent, stdin, and repeated scalar flags (#187, closes #147, #150, #151, #152):- A scalar
FileContentflag can only be given once on the CLI, and a second value reading-(acrossFileContentorFilewithstdin:"true") is a usage error. - Repeated scalar flags coerce every occurrence instead of only the last, so an earlier invalid value now fails the run.
- A scalar
Filewithexecutable:"true"resolves relative paths cleanly (#203, closes #188):./toolresolves in the working directory instead of$PATH, all executable paths are normalized to absolute paths, and missing/non-executable./namefails withErrValidationinstead ofErrCoerce.
Errors & diagnostics
- Source-based error categories (#190, closes #133, #162):
- Env-, config-, and default-sourced value failures match
ErrConfigonly (exit 1,IsUsageErrorfalse) instead ofErrCoerce/ErrValidation(exit 2). - This replaces the
v0.8.0change that made config-sourced feature errors usage errors. - Unexpected arguments and negated flags with values match
ErrParse; wrong path kinds matchErrValidation; missingRunnermatchesErrSchema.
- Env-, config-, and default-sourced value failures match
- Group conflict attribution &
--why(#192, closes #170):xor,oneof, andandconflicts whose members all come from env/config matchErrConfigonly (exit 1,IsUsageErrorfalse). Messages identify non-CLI members by source and CLI members by typed spelling;--whyno longer aborts on group conflicts.
- Updated error &
--why=jsonformats:--why=jsonreports bypassed search paths and overridden named files withpaths[].statusset to"skipped"(#137, #185).- Feature errors drop the
"config error:"prefix, name their source, and render compound/negated gates in words (#194). - Unknown-flag suggestions use
'unknown flag: --prot (did you mean "--port"?)'(#196).
✨ Features
- config: Add
conga.ConfigKeyCase(KebabCase,SnakeCase,CamelCase) for derived config keys (#183). - completion: Honour
LS_COLORSSGR codes and file-kind indicators (di,ln,or,ex,*<suffix>) in path predictors (#201, closes #156).
🐛 Bug Fixes
- api:
conga.TypeParseris again an alias offunc(string) (U, error), soRegisterTypeaccepts named function types as beforev0.8.0(#141). - completion: Write the bash lazy-load completion file under
${XDG_DATA_HOME:-$HOME/.local/share}and add anfpathfallback to the Homebrew zsh install steps (#141). - lint:
conga-lintprints related notes, and its-testflag wins over a same-named analyzer flag (#141). - validation: Compare
float32rangebounds atfloat64precision and report exactByteSizeoverflow limits and accepted units (#187, closes #147, #152). - cli: Allow repeated identical
-stdin claims on a single scalarFile/FileContentflag (#205). - config: Report errors in dotted namespace sections the same way as command sections (#205).
- errors: Let
errors.Isreach the underlying cause of config-sourcedErrConfigerrors (#205). - cli: Fix pluralization and natural list joining in
and-group errors, remove[command]fromRawArgsusage lines, and routehelp <unknown>through command suggestions (#140, #196...
v0.8.0
CONGA v0.8.0 overhauls the documentation site on docs.conga.sh, introduces conga.TypeParser, and ships diagnostics and completion installation fixes uncovered during the rewrite.
🚀 Highlights
- Documentation site rewrite: Rebuilt the documentation around tutorials, how-to guides, reference pages, and explanations, with rendered keyboard shortcuts via
starlight-kbd(#118, #120). - Named parser type & relative
conga-lintpaths: Exportedconga.TypeParserforRegisterTypecallbacks and switchedconga-lintdiagnostics to working-directory-relative paths (#118).
⚠ Breaking Changes & Migration
- Config-sourced feature errors & source attribution (#118):
- Invalid feature values read from a config file now fail as usage errors (exit 2) rather than
ErrConfig(exit 1), matching CLI and environment values. (Note: later superseded by source-basedErrConfigclassification inv0.9.0.) - Flag and feature value errors now include the environment variable or config key the value came from; update tests or callers matching the previous message text.
- Invalid feature values read from a config file now fail as usage errors (exit 2) rather than
✨ Features
- api: Export the
conga.TypeParsersignature forApp.RegisterType(#118). - lint: Print
conga-lintdiagnostic paths relative to the working directory (#118).
🐛 Bug Fixes
- errors: List accepted boolean values (including
1and0) in boolean parse error messages (#118). - completion: Correct and complete per-shell completion installation instructions (#118).
📚 Documentation
Full Changelog: v0.7.0...v0.8.0
Requirements: Go 1.27+ · Docs · pkg.go.dev
v0.7.0
CONGA v0.7.0 removes the blank-field form of envprefix and lets completion-enabled applications have names that start with a digit.
⚠ Breaking Changes & Migration
- Blank-field
envprefixremoved (#106, closes #100):_ struct{} `envprefix:"APP_"`fails schema build withErrSchema. Set the root prefix withapp.EnvPrefix("APP_"), and a subcommand's prefix with anenvprefixtag on itsCommand[T]field.- A subcommand
envprefixreplaces the inherited prefix rather than extending it. This was already the behaviour; the docs now say so.
✨ Features
- completion: A derived completion prefix that would start with a digit gains a leading underscore instead of failing at startup, so
7zreads_7Z_COMPLETION_DESCRIPTIONS. An explicitconga.CompletionEnvPrefixthat starts with a digit is still rejected (#104, closes #102).
📚 Documentation
- website: Clarify that
App.EnvPrefixdoes not apply toFeaturescontainers (#107).
Full Changelog: v0.6.0...v0.7.0
Requirements: Go 1.27+ · Docs · pkg.go.dev
v0.6.0
CONGA v0.6.0 adds implicit subcommands, completes trailing arguments with predictors, and makes -- end subcommand routing.
🚀 Highlights
- Implicit subcommands: An
implicit:"true"subcommand is selected by an operand that names no sibling, or by a flag only it declares, sotool ./script.tsruns astool run ./script.ts(#98). - Trailing argument completion:
DashArgsandRawArgsaccept apredictortag and complete after--or once raw mode begins (#95).
⚠ Breaking Changes & Migration
--ends subcommand routing (#95):- Operands after
--no longer name subcommands. They bind toDashArgsor positional arguments, or fail as unexpected arguments. DeclareDashArgson the command that should receive them.
- Operands after
- Trailing argument grammar is checked at startup (#95):
- Schema build fails with
ErrSchemawhen a command declares both positional arguments and subcommands, combinesRawArgswith command fields, puts optional or variadic positionals beforeRawArgs, or declares duplicate trailing collectors. - Move positionals to leaf commands, and use
DashArgsto forward arguments after--from a command with subcommands.
- Schema build fails with
- Flag-shaped tokens are no longer flag values (#95):
- A flag that takes a value no longer consumes a following token that looks like a flag, or
--.--name --verbosenow fails withflag requires an argument: --name(exit 2). Pass such values attached:--name=--verbose.
- A flag that takes a value no longer consumes a following token that looks like a flag, or
✨ Features
- cli: Add
implicit:"true"subcommands, marked(default)in help (#98). - completion: Complete
DashArgsandRawArgswithpredictortags, and offer no candidates after--when the command has nowhere to bind them (#95).
🐛 Bug Fixes
- cli: A declared
--helpor--versionflag also disables the synthesized-hor-Vshort for that command chain (#97).
📚 Documentation
- website: Document implicit subcommand routing (#103).
Full Changelog: v0.5.0...v0.6.0
Requirements: Go 1.27+ · Docs · pkg.go.dev
v0.5.0
CONGA v0.5.0 renames the group help-heading tag to section and rejects flag groups and tags that previously had no effect.
⚠ Breaking Changes & Migration
grouptag renamed tosection(#91, closes #87):- Rename
group:"..."tosection:"..."on flags, commands, and built-in command fields.groupis now an unknown tag and fails schema build withErrSchemaunless allowed withapp.AllowTags("group").
- Rename
- Flag groups that had no effect are rejected (#91):
- A one-member
xororandgroup, a one-memberoneofgroup on a flag other than aCounter, and a flag in both an exclusive (xororoneof) group and anandgroup fail schema build withErrSchema. - Remove the group tag, add the missing members, or use
RequiredFlaginstead of a one-memberoneof.
- A one-member
- CONGA tags on plain fields are rejected (#91):
- CONGA tags on fields that are not containers used to be ignored. They now fail schema build with
ErrSchema. Remove the tags, or make the field a container.
- CONGA tags on fields that are not containers used to be ignored. They now fail schema build with
📚 Documentation
- website: Document flag grouping, built-in short flags, and help wrapping (2d443b4).
Full Changelog: v0.4.0...v0.5.0
Requirements: Go 1.27+ · Docs · pkg.go.dev
v0.4.0
CONGA v0.4.0 wraps help to the terminal width, adds oneof flag groups and short flags for the built-in help and version flags, and names completion environment variables after the application.
🚀 Highlights
- Help wrapping: Help output wraps to
COLUMNS, the terminal width, or 100 columns, and aligns columns by terminal cell width (#88). oneofflag groups: Exactly one member of aoneofgroup must be set. Usage shows the group as(--input-file=PATH | --input-url=URL), and completion hides the other members once one is given (#88).- Built-in short flags:
App.HelpShortFlagandApp.VersionShortFlagbind a short rune to--helpand--version(#88). - App-named completion variables: Completion toggles are read from
<APP>_COMPLETION_*, andconga.CompletionEnvPrefixoverrides the prefix (#82).
⚠ Breaking Changes & Migration
API changes
WhyJSONandRegisterTypeOptionrenamed (#84):- Replace
conga.WhyJSON()withconga.WhyOptionJSON()and theconga.RegisterTypeOptiontype withconga.RegistrationOption.
- Replace
Schema & startup guards
RequiredFlagrejectsdefaultandxor(#88):- Either tag on a
RequiredFlagfails schema build withErrSchema. UseOptionalFlagfields in aoneofgroup instead.
- Either tag on a
congadirectives removed (#88):conga:"ignore"andconga:"-"no longer exclude a field. Plain fields that are not containers need no tag. Remove from the struct any container field CONGA should skip.- Any remaining
congatag is an unknown tag and fails schema build withErrSchemaunless allowed withapp.AllowTags("conga").
Configuration
- Completion environment variables named after the application (#82, closes #81):
CONGA_COMPLETION_ALIASESandCONGA_COMPLETION_DESCRIPTIONSare now<APP>_COMPLETION_ALIASESand<APP>_COMPLETION_DESCRIPTIONS, where<APP>is the application name in upper snake case. Rename them in shell configuration, or passconga.CompletionEnvPrefix(...)toEnableCompletionto choose the prefix.
✨ Features
- cli: Wrap help output to the terminal width and align tables by terminal cell width (#88).
- cli: Add
oneofgroups for exactly-one flag sets (#88). - cli: Add
App.HelpShortFlagandApp.VersionShortFlagfor built-in short flags; collisions with declared shorts fail schema build (#88). - cli: Help, usage, and version output use the configured application name instead of the invoked binary name (#88).
- completion: Read completion toggles from application-prefixed variables and add
conga.CompletionEnvPrefix(#82, closes #81). - completion: Offer flags only after
-in every shell, not at a bare space; set<APP>_COMPLETION_BARE_SPACE_FLAGSor thebare-space-flagszstyle to restore them. Zsh also resolves~namenamed directories (#86).
Full Changelog: v0.3.0...v0.4.0
Requirements: Go 1.27+ · Docs · pkg.go.dev
v0.3.0
CONGA v0.3.0 replaces ConfigLoader with the Bootstrapper lifecycle hook and adds completion toggles for aliases and descriptions.
🚀 Highlights
Bootstrapperlifecycle hook:Bootstrap(ctx, *conga.Bootstrap)runs before config resolution. It can load.envfiles from flag-derived paths and supply aConfigDocumentthat overlays file configuration key by key (#70).- Completion toggles:
CONGA_COMPLETION_ALIASESandCONGA_COMPLETION_DESCRIPTIONScontrol whether aliases and descriptions appear, in every shell (#76).
⚠ Breaking Changes & Migration
-
ConfigLoaderreplaced byBootstrapper(#70):conga.ConfigLoader,ConfigLoaderFunc, andConfigContextare removed. ImplementBootstrap(ctx context.Context, b *conga.Bootstrap) erroron the root command, build the sameConfigDocument, and pass it tob.SetConfig.b.LookupEnvandb.PathreplaceConfigContext.LookupEnvandCommandPath.- A
ConfigLoaderreplaced configuration file resolution.SetConfigoverlays file configuration key by key instead, so files found through decoders and search paths now load as well.
// Before app.ConfigOptions(conga.ConfigLoader(func(ctx conga.ConfigContext, root *CLI) (*conga.ConfigDocument, error) { return loadDocument(root) })) // After func (c *CLI) Bootstrap(ctx context.Context, b *conga.Bootstrap) error { document, err := loadDocument(c) if err != nil { return err } b.SetConfig(document) return nil }
✨ Features
- completion: Add the
CONGA_COMPLETION_ALIASESandCONGA_COMPLETION_DESCRIPTIONStoggles, mark aliases on the wire, and honour the zshverboseandshow-aliasesstyles (#76). (Renamed after the application inv0.4.0.)
🐛 Bug Fixes
- completion: Honour the zsh
list-separatorstyle inlist-colorspatterns, so both columns keep their colours (#77).
📚 Documentation
- website: Reframe the bootstrap docs as domain document loading (#78).
Full Changelog: v0.2.0...v0.3.0
Requirements: Go 1.27+ · Docs · pkg.go.dev
v0.2.0
CONGA v0.2.0 adds per-feature environment variables, makes struct tag validation always on, and lets applications replace the writer that .env loading uses.
🚀 Highlights
- Per-feature environment variables:
envprefixon aFeaturescontainer derives one variable per feature, feature fields acceptenvtags, and root help lists each feature's variables (#53, #57). - Always-on tag validation: Unknown struct tag keys always fail schema build, and
app.AllowTagsis the only way to accept extra keys (#58). - Injectable
.envwriter:App.SetenvFuncreplaces theos.Setenvcall thatApp.Dotenvuses, so tests can passt.Setenv(#55).
⚠ Breaking Changes & Migration
App.StrictTagValidationremoved (#58):- Struct tag validation is always on. Delete
StrictTagValidation(...)calls, and list any foreign tag keys withapp.AllowTags("<key>", ...), which matches keys exactly. - The
conga:"allow-unknown-tags"andconga:"recurse"directives fail schema build withErrSchema. Replace them withapp.AllowTags. conga-lintdrops its-strictflag.
- Struct tag validation is always on. Delete
envprefixon aFeaturescontainer derives one variable per feature (#53, closes #49):envprefix:"APP"used to derive one combinedname=valuemap variable,APP_<FLAG>, from the container's flag name. It now derivesAPP_<FEATURE>for each feature.- To keep a single combined variable, name it with
env:"<NAME>"on the container instead ofenvprefix.
{{env}}inFeatureshelp text (#57):{{env}}now substitutes only the container's combined-mapenvvariable. A container whose only environment surface isenvprefixor fieldenvtags fails schema build withErrSchema.- Remove
{{env}}from such help text. Root help now lists each feature's variables as[env: ...].
✨ Features
- features: Feature fields accept
env:"NAME1,NAME2"andenv:"-", and an invalid per-feature value is a usage error naming the variable (#53, closes #49). - features: Root help lists each feature's environment variables as
[env: VAR1, VAR2](#57). - dotenv: Add
App.SetenvFuncto replace the writerApp.Dotenvuses for loaded variables (defaultos.Setenv) (#55, closes #51). - config: Config-file flag help lists the registered decoders, for example
[decoders: .json, .yaml](#59). - why: Help shows
--why[=FORMAT], and completion offers--why=<format>, only when JSON output is enabled withWhyJSON()(#61). - cli: Built-in help, version, and completion command fields accept
aliasesandgrouptags (#66). (groupwas renamedsectioninv0.5.0.)
🐛 Bug Fixes
- cli: Synthesized help, version, and completion commands follow the app-wide built-in visibility toggles, and disabled
--whyand--completionflags no longer appear on subcommands (#64).
📚 Documentation
- website: Document
--whyflag help and completion rendering (#67).
Full Changelog: v0.1.1...v0.2.0
Requirements: Go 1.27+ · Docs · pkg.go.dev