Specify config file with CLI?

[WoosterInitiative]

There is so much good here, but everything I try seems to hit some snag that makes me have to back up.

Is there a way that I haven't figured out to be able to pass a config file on the command line? Perhaps as -c or --config? This might help with subcommands (though I haven't fully investigated that) but would allow for better package use and allows me to pass a different config file for different purposes (think API/scraping access for multiple users, like for use with amazon-orders).

I've tried doing it brute-force with Typer and really thought I'd found something here, but I can't quite make it work; am I missing something? Is it something you might consider if I put some work into it and did a PR?

[WoosterInitiative]

I immediately found the undocumented default keyword argument, though I still haven't thought of an elegant way to have that use an argument for the path name.

[e3rd]

I'd be really glad for any PR.

--config flag

The way I'd like to be is to add add_config option (by default I think False) that would add the flag --config flag you mentioned the same way as add_verbose works. The alternate way should be MININTERFACE_CONFIG= env variable. These two should work if config_file=True.

I'd like the underlying CLI library to stay tyro instead of Typer, a year ago, I did a big comparison of CLI tools (25+) and tyro seemed to me better than Typer ((here)[https://blog.nic.cz/2024/05/15/parsovani-cli-v-pythonu-po-trech-letech/] but in Czech only).

subcommands config
I think this might be implemented by modifying cli_parser.py / _create_with_missing method to take a list, and not a single dataclass.

For this set-up https://cz-nic.github.io/mininterface/Cli/#mininterface.cli.Command--an-example-of-command-usage , the config file might look that way:

subcommand1:
  my_local: 5
  common: 7
subcommand2:
  common: 6

Do you find it a good idea?

another snags
What other snags have you hit? :) I'd be curious for the whole list.