Mature CLIs ship shell completions (bash/zsh/fish): type redential s<TAB> and get scan submit status. Worth having eventually, but this repo has a hard constraint that makes it a design discussion first: no new dependencies without written justification, and the usual completion libraries are exactly that.
Questions to settle before any code:
- Can commander's built-in metadata drive a hand-rolled
redential completion <shell> generator with zero dependencies? (Print a static script per shell; users source it from their rc file.)
- Which shells matter enough to maintain? (bash + zsh covers most; fish is a nice-to-have.)
- Where does it get documented, and does
npm install -g have any sanctioned hook for offering setup (given the repo's zero-postinstall rule, likely no; docs-only setup).
Opinions and prior art welcome. This graduates to an implementation issue once the zero-dependency approach is agreed.
Mature CLIs ship shell completions (bash/zsh/fish): type
redential s<TAB>and getscan submit status. Worth having eventually, but this repo has a hard constraint that makes it a design discussion first: no new dependencies without written justification, and the usual completion libraries are exactly that.Questions to settle before any code:
redential completion <shell>generator with zero dependencies? (Print a static script per shell; users source it from their rc file.)npm install -ghave any sanctioned hook for offering setup (given the repo's zero-postinstall rule, likely no; docs-only setup).Opinions and prior art welcome. This graduates to an implementation issue once the zero-dependency approach is agreed.