Right now, we use predetermined tools and we assume any tool passed to the option works like
the default tool for that option. Users should be able to set entire commands, although some commands are quite complicated (see find or compress).
These would require interpolations within themselves, for example xz needs -T #{@paths.manifest} so it could do something like -T %{manifest} or -T $(manifest).
This would enable users to use fzf instead of find for the search step, for example, which at the moment would not work at all since fzf's options are wildly different.
This causes Command and it's subclasses to be obsolete, allowing us to rename Action to Command to align more with the command pattern as laid out in #20.
Right now, we use predetermined tools and we assume any tool passed to the option works like the default tool for that option. Users should be able to set entire commands, although some commands are quite complicated (see
findorcompress).These would require interpolations within themselves, for example
xzneeds-T #{@paths.manifest}so it could do something like-T %{manifest}or-T $(manifest).This would enable users to use
fzfinstead offindfor the search step, for example, which at the moment would not work at all sincefzf's options are wildly different.This causes
Commandand it's subclasses to be obsolete, allowing us to renameActiontoCommandto align more with the command pattern as laid out in #20.