We generate click commands & groups for the tools stored in our file tree by recursing down our file tree generating click groups for directories and click commands for tools as they're found. This is 1) a very tight coupling between our file structure and click object creation and 2) makes it very difficult to create the click commands with desired parameters.
The way arguments/options are added to the CLI commands that represent tools is clunky and unworkable. Currently an arguments argument is added to all tool commands generated (also https://github.com/alces-software/adminware/blob/develop/src/click_tools.py#L69) and thus each time the file tree is explored this way, an arguments argument is returned. This is often not needed for the context and it may be necessary to add more or different arguments/options in the future.
It not easy to create click commands for file tree directories - as opposed to tools. This is not the usually desired affect but will be needed for auto completion for certain commands - e.g. view tools
Apologies if this seems a little like word salad - there's a lot of overlap for a lot of this terminology.
We generate click commands & groups for the tools stored in our file tree by recursing down our file tree generating click groups for directories and click commands for tools as they're found. This is 1) a very tight coupling between our file structure and click object creation and 2) makes it very difficult to create the click commands with desired parameters.
3 symptoms of this are:
view toolsApologies if this seems a little like word salad - there's a lot of overlap for a lot of this terminology.