体验:all-cli kubectl current 没有 context/namespace 时不说看 status
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 24
Description
all-cli kubectl current 在 context 和 namespace 都空时,最多把 kubectl 的 error 打到 stderr,然后 return nil。stdout 为空,也不说下一步去看 all-cli kubectl status。
k9s current 空结果会写 no k9s context. Check: all-cli k9s status。mise current 会写 See install status: all-cli mise status。kubectl 缺这一步。
TestKubectlCurrentPlainError 只覆盖 current-context 失败但仍有 namespace 的情况,不会走到空结果。
这是体验缺口:空结果应指出 all-cli kubectl status。不要改 use/list/namespace 语义。
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 all-cli kubectl current command and inspect the path where both context and namespace are empty; compare its output with k9s current and mise current. Run TestKubectlCurrentPlainError, then add coverage for the empty-result case and verify that stdout points to all-cli kubectl status without changing use, list, or namespace semantics.
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
- Clearly specified
- Newbie friendliness
- 76/100