Currently it looks like this:
Usage: gitja [-c|--config CONFIG] [-q|--quiet] [-f|--force] [-i|--init]
[-v|--version]
Available options:
-c,--config CONFIG Configuration file to use (Default: ./config.dhall).
-q,--quiet Suppress non-error output.
-f,--force Force regeneration of all files.
-i,--init Create a template and config in the current folder.
-v,--version Print the gitja's version.
-h,--help Show this help text
Conceptually gitja has two subcommands:
run: actually run gitja, which involves taking a template folder and generate and output folder using data from git repos (much of this info is defined in config.dhall. This then owns:
--force (by default some outputs are skipped, such as the webpage for a commit, because it won't change unless you change the templates, so --force will regen it all)
--quiet (by default it prints out which files are getting written to. TBH this should probably be default and replaced with --verbose)
--config - use a config other than ./config.dhall
init: create a 'bare' template folder in the current folder, along with a default config, so users can get started editing those
So we should adjust the clap CLI setup to use these two subcommands.
Currently it looks like this:
Conceptually gitja has two subcommands:
run: actually run gitja, which involves taking a template folder and generate and output folder using data from git repos (much of this info is defined inconfig.dhall. This then owns:--force(by default some outputs are skipped, such as the webpage for a commit, because it won't change unless you change the templates, so --force will regen it all)--quiet(by default it prints out which files are getting written to. TBH this should probably be default and replaced with--verbose)--config- use a config other than./config.dhallinit: create a 'bare' template folder in the current folder, along with a default config, so users can get started editing thoseSo we should adjust the
clapCLI setup to use these two subcommands.