mosquito / argclass / 35469736840

100%

push

github

Config generation and config files cover subparsers (#52)

* docs: define config sections for subparsers

A subparser section follows the attribute path, the same rule that
groups use. Nested groups and nested subparsers extend the path with
a dot. This fixes the on-disk layout before the reader and the config
generators learn to walk subparsers.

* Read parent config files inside subparsers

A subparser used to read only its own config_files, so a section such
as [serve] in the root parser's file never reached the subcommand.
The root parser now hands its config layers (the config_argument file,
inherited layers, config_files) to each subparser with the subparser's
attribute path as the section prefix. Groups inside a subparser and
nested subparsers extend the prefix with a dot.

Priority inside a subparser, highest first: config_argument file,
parent config_files, the subparser's own config_files, declared
defaults. Env vars and CLI arguments still override all of them.

* Walk subparsers in config generators

iter_config_fields now descends into __subparsers__ after the groups
of each node. A subparser becomes a section named after its attribute
([serve], [serve.db], [serve.worker]), the layout the readers expect,
so one generated file covers the whole command tree.

ConfigField gains subparser_path. Its dest stays the argparse dest of
the owning subparser, because a subparser is a separate
ArgumentParser and its dests do not carry the subcommand name.

ConfigGenerator(include_subparsers=False) restores the old behaviour
of dumping only the root parser and its groups.

* Scope the parse namespace when dumping subparsers

argparse parses a subcommand into a fresh namespace and copies it
into the parent only after the subcommand finished. A namespace seen
by GenerateConfigAction therefore holds the values of the parser that
owns the Action and of the selected subparsers below it. The walker
now reads the namespace only for those parsers; an unselecte... (continued)

616 of 616 branches covered (100.0%)

Branch coverage included in aggregate %.

100 of 100 new or added lines in 4 files covered. (100.0%)

1758 of 1758 relevant lines covered (100.0%)

4.99 hits per line