Repository navigation
feat(lookup): always enable path completion even if a spec isn't registered - #176
Conversation
|
yeah you're right also a bug, the path completion block runs before checking if a spec exists, so for commands that already have a spec (like git), it replaces the entire spec with a stub if any files match. Should be guarded with if !exists && config.Get().Core.PathCompletion && partial != "" && !strings.HasPrefix(partial, "-") {Also the partial redeclaration inside Additional: |
I've updated the PR, this actually made the implementation much cleaner |
versenilvis
left a comment
There was a problem hiding this comment.
change the title to conventional style so I can merge as a commit
Currently, path autocompletion doesn't work unless a spec is registered for a command. I think we shouldn't have to register a spec for a command just to get path completion. This adds the option to always complete paths