Skip to content

[Request]: UX: add whitespace between subcommand groups for container --help. #1513

@jglogan

Description

@jglogan

Feature or enhancement request details

Help would be a bit more readable with whitespace between groups.

We should look into whether there's any way to do this with swift-argument-parser config; otherwise, Application.printModifiedHelpText() where we could regex replace before adding plugin subcommands with pluginLoader.alterCLIHelpText().

OVERVIEW: A container platform for macOS
USAGE: container [--debug] <subcommand>
OPTIONS:
  --debug                 Enable debug output [environment: CONTAINER_DEBUG]
  --version               Show the version.
  -h, --help              Show help information.

CONTAINER SUBCOMMANDS:
  create                  Create a new container
  delete, rm              Delete one or more containers
  exec                    Run a new command in a running container
  export                  Export a container's filesystem as a tar archive
  inspect                 Display information about one or more containers
  kill                    Kill or signal one or more running containers
  list, ls                List running containers
  logs                    Fetch container logs
  run                     Run a container
  start                   Start a container
  stats                   Display resource usage statistics for containers
  stop                    Stop one or more running containers
  prune                   Remove all stopped containers

IMAGE SUBCOMMANDS:
  build                   Build an image from a Dockerfile or Containerfile
  image, i                Manage images
  registry, r             Manage registry logins

VOLUME SUBCOMMANDS:
  volume, v               Manage container volumes

OTHER SUBCOMMANDS:
  builder                 Manage an image builder instance
  network, n              Manage container networks
  system, s               Manage system components

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

Labels

nextMust-have items for current and next milestoneuxUser experience features and fixes.
No fields configured for Feature.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions