at_args package for cli tools to depend on.

[XavierChanth]

Lead: @XavierChanth

Is your feature request related to a problem? Please describe. Installing the application via git is not ideal if we would like to make these tools available to external developers.

Describe the solution you'd like Rather than installing from git and running the dart files, make the tools available via pub.dev similar to at_app. At the very least, I would like to see this for at_cli.

Changes required per package:

• [ ] Update pubspec.yaml to publish as a binary
• [ ] Ensure that relative file management is handled correctly (i.e. the config file for at_cli)
  • [ ] Use "$HOME/.atsign" when local config directory is unavailable.
• [ ] Migrate our tools to extend Command from args (so that our tools can be extended)

Additional thoughts:

• Include some documentation about our preferred ways of logging/printing.
  • Non-debugging things should be hidden by default, and logged using AtLogger.
  • Everything else can use stdout + chalk

Packages:

• [ ] at_cli
• [ ] at_pkam
• [ ] at_dump_atKeys
• [ ] at_cram
• [ ] at_ve_doctor
• [ ] at_talk

Describe alternatives you've considered N/A

Additional context N/A

[XavierChanth]

Depending on my available time, I will try to start this for at_cli during PR 32.

[XavierChanth]

To simplify the approach I will begin work on an at_args package which will help us accomplish this.

[XavierChanth]

Working on this in PR43 alongside at_daemon

[XavierChanth]

Continuing in PR 45

[XavierChanth]

I doubt this ticket will ever be worked on.