Unable to generate badger completions without --dir flag
Open
Beginner friendly
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 21.8k
- Forks
- 1.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 9
Description
Describe the bug
Unable to generate badger completions without --dir flag
To Reproduce
Steps to reproduce the behavior:
- $ badger completion bash
Expected behavior
I expected the bash completion script to be output without requiring the --dir flag.
Affects badger bash/fish/powershell/zsh output.
Screenshots
Error:
--dir not specified
Environment
- OS: Arch Linuix x64
- Language
- Version 25.3.4
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running badger completion bash and checking the completion command's handling of the --dir flag. Trace the badger completion entry point for bash, fish, PowerShell, and zsh; done means each command emits its completion script without requiring --dir.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100