- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 18
 
Open
Labels
enhancementNew feature or requestNew feature or request
Description
Some CLIs, such as Rust's Cargo, boast a suite of subcommand aliases for common commands such as cargo b for cargo build, and cargo r for cargo run. I believe similar aliases would be for a great QoL improvement for Swift Bundler users. Especially if paired with alias sbun="swift-bundler", which I've grown quite fond of lately.
sbun r # sbun run
sbun bun # sbun bundle (can't be sbun b because I want to support 'sbun build' in future)
sbun t # sbun test (future command)
sbun c # sbun create (is this one worth it given that we don't expect people to run it very often?)As you can see from those 4 examples, there are quite a few factors we need to take into account when deciding which subcommands deserve aliases, and how short we should make the said aliases. Here are the factors that come to mind:
- How often are people expected to run the command?
 - How clear is it which subcommand the alias refers to?
 - How likely is it that we'll have other commands that clash with the chosen alias in future?
- How likely is it that the hypothetical clashing commands would seem more 'primary' than the existing one?
 
 - How core is the subcommand to Swift Bundler's CLI?
 
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request