体验：all-cli k9s current 没有上下文时不说看 status
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 24
Description
体验
all-cli k9s current 在没有 kube context / namespace / k9s config 时，stdout 是空的。stderr 可能有 kubectl 报错，但不说下一步。人不知道该跑 all-cli k9s status。
k9s 没有 use。空 current 之后只能去看 status。
不要和 #71（doctor 无诊断）或 #72（gh use 缺参）混在一起。
期望
非 JSON 模式下，三个字段都空时，stderr 写 no k9s context. Check: all-cli k9s status。
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 at the implementation and output path for all-cli k9s current, then reproduce the case with no kube context, namespace, or k9s config. In non-JSON mode, done means stderr contains no k9s context. Check: all-cli k9s status when all three fields are empty.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100