Closed rzmk closed 20 hours ago
If #1307 is completed then this could potentially be automated by comparing the JSON outputs (e.g., between versions, manual workflows, etc.) and generating the necessary files. Users could then also generate the latest completions from master and this could lead to a command that automatically generates and/or enables completions (e.g., qsv completions
).
This could be further automated by extending qsv-docopt as noted in #1307
See Resolved in #1915.qsv enum
for new changes.
Remove See #1951.--ollama
for qsv describegpt
.
Is your feature request related to a problem? Please describe.
The currently available Bash completions files in
contrib/bashly
are set up for qsv v0.128.0. Thecontrib/bashly/src/bashly.yml
andcontrib/bashly/completions.bash
files must be updated for the upcoming qsv v0.129.0 release (steps explained in that directory'sREADME.md
).Describe the solution you'd like
Update
contrib/bashly/src/bashly.yml
with all the commands/subcommands/options/etc. for qsv v0.129.0 and then generate the updatedcontrib/bashly/completions.bash
file.Additional context
Identifying all of the changes (new/modified commands/subcommands/options/etc.) that have been made since v0.128.0 is required.