Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Create a package subcommand in leo CLI #596

Closed
damirka opened this issue Feb 2, 2021 · 2 comments
Closed

[Feature] Create a package subcommand in leo CLI #596

damirka opened this issue Feb 2, 2021 · 2 comments
Assignees
Labels
feature A new feature.

Comments

@damirka
Copy link
Contributor

damirka commented Feb 2, 2021

🚀 Feature

I suggest adding leo package subcommand. So Aleo PM related commands would look like:

leo package add <package>
leo package remove <package>
leo package login ...
leo package publish
leo package search ... 
# etc

If this looks long, we can shorten package to pkg or think of a different naming.

Motivation

We already have many and will be having even more commands within leo CLI. Also some commands are API heavy (and involve logging in) and some only use algorithms. By splitting commands into smaller groups we help understanding them by first look and also split logic within the CLI application.

So the enduser clearly sees which commands may require Aleo PM credentials and which can be run locally.

Implementation

Subgrouping can be easily implemented within #584 if it receives a green light due to StructOpt flatten feature.

@damirka damirka added the feature A new feature. label Feb 2, 2021
@damirka damirka self-assigned this Feb 2, 2021
@damons
Copy link

damons commented Feb 2, 2021

This makes sense to me.

@damirka
Copy link
Contributor Author

damirka commented Feb 5, 2021

Won't do due to this comment.

@damirka damirka closed this as completed Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants