-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for CLI command completions #693
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #693 +/- ##
==========================================
+ Coverage 99.61% 99.63% +0.01%
==========================================
Files 89 89
Lines 6166 6222 +56
==========================================
+ Hits 6142 6199 +57
+ Misses 24 23 -1
... and 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
Tryin to please code quality checkers
Increase test coverage and more check outputs
The completion response is not very instantaneous but quite usable. On my laptop I tried to optimize startup speed by moving some import statements into functions in |
Kudos, SonarCloud Quality Gate passed!
|
The response time of completions will be improved by #696 to ~0.3 seconds or slightly less. |
Adds support for tab-key completions for commands, options and project id and vocabulary id parameters via Click mechanism.
A user needs to enable the support as instructed in README.md, i.e. by sourcing the completion script, either manually for every terminal session or automatically for all new sessions by the sourcing the script in a shell startup file (instructed to use
.bashrc
).To produce the completion script the
annif completion
CLI command is added. This seems to be the standard way that many CLI tools use: pip, dvc, helm.Implements #684.