Provide shell auto‑completion for the CLI - #81
Closed
kael-developer[bot] wants to merge 1 commit into
Closed
Conversation
Implemented by Kael AI Agent
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Generate auto‑completion scripts (Bash, Zsh, Fish) for the command‑line interface using Click's built‑in support or argcomplete. Package the scripts so users can easily enable tab‑completion, improving usability and discoverability of commands and options.
Implementation summary
We see a syntax issue at line 170: after return getConfigFile(confDir) there is no newline before comment, also stray closing brace after 194? At line 194 is '}' extra. The file now has mismatched braces. Need to fix: GetConfigFilePath should be before getConfigFile, and we need proper formatting. Also need to remove stray '}' at end of file (there's an extra). Let's edit to correct.
Closes #76