tome-cli

A rewrite of sub and tome and my fork of tome but with a different internal implementation in order to support:

1. Improved auto-completion
2. Improved usage/help outputs
3. Faster development
4. Testable interfaces

Usage

# shorthand syntax via bash wrapper script
tome-cli --executable kit alias --output ~/bin/kit

# further uses of kit script have embedded values for TOME_ROOT and TOME_EXECUTABLE
kit completion fish | source
kit path to file
kit pat<TAB>

# Long form
export TOME_ROOT=examples
tome-cli exec path to file
tome-cli help path to <TAB>
tome-cli completion fish | source

# Setup tab completion
tome-cli completion fish | source
eval "$(tome-cli completion zsh)"

# See instructions for a command
tome-cli completion --help

See docs for expanded instructions

Features

• Organize a folder of scripts into a CLI sdk
• Any language is supported via normal script #!
• Usage text extracted from script header if USAGE: is included in leading comments
• Full help text extracted as lines from USAGE: to first empty line
• Builtin alias generator allows for embedding configuration flags via tome-cli alias
• Auto completion of:
  • subcommands (exec, help, etc)
  • root folder's folder names
  • root folder's scripts
  • root script's flags and arguments (when they satisfy the --complete and TOME_COMPLETION interface)
• Gitignore like syntax for ignoring scripts by using a .tomeignore file at base of root folder example

Capabilities

• exec scripts in a directory
• auto-complete script names (https://github.com/spf13/cobra/blob/main/site/content/completions/_index.md)
• include description into auto-complete if shell supports it
• cross compilation via goreleaser
• [o] test harness for the commands
  • e2e tests wrapped in deno unit tests
  • Add tests for backwards compatibility with prior tome
  • cobra testing for commands
• supports aliasing tool to shorthand name
• Determines root folder based on: 1. cli flag 2. env var named after binary (eg auto detect and use PARROT_ROOT if alias name is parrot)
• Use https://github.com/spf13/cobra/blob/main/site/content/completions/_index.md#creating-your-own-completion-command to override and rename from tome-cli to whatever the binary name is on their system
• add tome compatibility layer for transition or include shell script shim
• Setup changelog tooling (chglog init)
• Respects a .gitignore type file in root of project to determine what to complete/execute (https://github.com/sabhiram/go-gitignore)
• auto-complete script arguments (scripts that include the text TOME_COMPLETION which are tab completed will try to get autocompletes from the script via executing it with --completion)
• injects TOME_ROOT into tooling as env var and TOME_EXECUTABLE
• Add level and k/v style logging
• Add instructions to README
• Generate a docs folder for more full instructions (https://umarcor.github.io/cobra/#generating-markdown-docs-for-your-own-cobracommand)
• See if there's utility in ActiveHelp https://umarcor.github.io/cobra/#active-help
• pre-hooks (hooks.d folder will be sourced in order or executed before the real script)
  • https://umarcor.github.io/cobra/#prerun-and-postrun-hooks
• Help
  • Help on a directory should print the shorthand outputs of all subcommands in that folder tree
  • Suppress the builtins from final tab output if we have 1+ matches against directory (bash and fish at least have defective output)

	// The *Run functions are executed in the following order:
	//   * PersistentPreRun()
	//   * PreRun()
	//   * Run()
	//   * PostRun()
	//   * PersistentPostRun()

Non Features

• Does not support sourcing scripts into shell environment because it adds implementation complexity for other core commands