asdf-vm / asdf-vm/asdf

Go version extension commands usage don't match bash version/docs/cli help output

Open
#2,150 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Go
Stars
25.6k
Forks
941
Avg merge
9h 24m
Merged PRs (30d)
3

Description

### Is your feature request related to a problem? Please describe

In 0.18 you use `asdf cmd []` whereas in the older version you could call `asdf []` directly.

In addition, the docs and the cli still show the old way.

I liked the old way. Is there are a reason why the `cmd` command was introduced?

### Describe the proposed solution

I have made a fork with a patch that re-introduces the old way, but also keeps the new way. Is this something work merging, or would the core rather not bring that to life.

### Describe similar `asdf` features and why they are not sufficient

none. `asdf cmd` worked as expected, it just feels more clumsy to me.

### Describe other workarounds you've considered

none

Contributor guide

Open the contributing guide

Research direction

Compare the Go version's `asdf cmd []` entry point with the older Bash-style direct `asdf []` invocation, then inspect the CLI help and documentation that still show the old form. Done means the project has a clear decision on whether both forms are supported and the behavior, help output, and docs agree.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, go
Domain
cli, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.