Edit: disregard, handled in #240

We should also add flag completions for flags like --format and --encoding

In the link PR branch, I've refactored flags like those that consist of a static set of choices, so keep that in mind. For the --type argument to link, this works:

	cobra.CheckErr(linkCmd.RegisterFlagCompletionFunc("type",
		func(_ *cobra.Command, _ []string, _ string) ([]string, cobra.ShellCompDirective) {
			return typeChoice.choices, cobra.ShellCompDirectiveDefault
		},
	))

where typeChoice.choices is equivalent to []string{"node", "document"}

Just curious, what happens if you delete the database file before attempting to [tab][tab]? Or if you specify a different location for the database file using --cache-dir or the BOMCTL_CACHE_DIR environment variable?

Just curious, what happens if you delete the database file before attempting to [tab][tab]? Or if you specify a different location for the database file using --cache-dir or the BOMCTL_CACHE_DIR environment variable?

Had a couple ideas for a possible (and maybe only partial) solution using viper:

• Try checking the value of the --cache-dir flag dynamically by using viper.GetString("cache_dir") to see if it's already captured by default before execution. It should at least have the value of BOMCTL_CACHE_DIR if it's already set in the environment
• If that doesn't work, try setting the viper cache_dir config value by either:
  • updating the initCache function to set it by checking the command string for the value captured by --cache-dir[= ](.*) (doesn't have to be regex, just as an example)
  • adding an autocomplete function for --cache-dir that basically just does normal filesystem completions but also runs viper.Set("cache_dir", ...)

If nothing in the second option works, I think the first is probably good enough for now