体验:kubectl/docker use 缺参只报 accepts 1 arg,不说 list
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 23h
- Merged PRs (30d)
- 24
Description
用户路径
all-cli kubectl use
all-cli docker use
Cobra 默认报:
accepts 1 arg(s), received 0
不说要 context 名,也不说 all-cli kubectl list / all-cli docker list。
本轮不碰已有 issue:#54 doctor/diagnose、#55 options、#56 catalog 无匹配、#57 catalog 发现、#58 schema 缺参、#59 grok、#60 describe 缺参。也不改正在改的 catalog/describe。
摩擦点
use 是切上下文。缺参时人不知道先 list。schema/describe 已经改成说明性错误,use 漏了。
建议改动
kubectl use/docker use缺参时说明要 context,并指向对应list。
不在范围内
- 不改 schema/describe。
- 不 push、不开 PR、不 merge。
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 command definitions for kubectl use and docker use, then trace how each handles a missing context argument. Update the missing-argument errors to name the required context and point to the corresponding list command; done means both paths provide that guidance without changing schema, describe, catalog, or other excluded commands.
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
- 78/100