体验：all-cli aliyun current 没有 profile 时 stdout 为空

Open Beginner friendly
#75 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
cli

Research direction

Start with the all-cli aliyun current command and compare its human-readable and JSON output paths. Reproduce the case where aliyun configure list has no profile or fails, then verify that human-readable mode suggests all-cli aliyun list and all-cli aliyun status while JSON still returns an empty current object.

Written by the indexing model from the issue text.

Description

User path

README 把 all-cli aliyun current 写成看当前 Aliyun profile 的入口。没装 aliyun、或 aliyun configure list 没有 profile 时，人会直接跑这条命令。

Friction

人读输出只打印非空的 profile / region / language / valid。Current 在 list 失败或没有 profile 时返回空 map，stdout 完全空白，退出码仍是 0。错误只在 stderr。不说去 all-cli aliyun list 或 all-cli aliyun status。JSON 仍给空 current，脚本路径可以保持。

Suggested change

人读模式在没有任何字段时打印下一步：all-cli aliyun list 和 all-cli aliyun status。不要改 JSON 契约。

Dominant language
Go
Stars
1
Forks
0
Avg merge
7d 23h
Merged PRs (30d)
24

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oldwinter/all-cli

All issues in oldwinter/all-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.