-
-
Notifications
You must be signed in to change notification settings - Fork 169
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] Adding a progress bar for CLI Commands to show the progress status #1410
Comments
Great feature proposal @AayushSaini101 ❤️ |
Hey @AayushSaini101 if i can take this up, as you are already engaged in many issues |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
@ibishal i'd love to join you. |
Feel free to create a PR on this issue |
Why do we need this improvement?
It would be good if we can add progress bar when we execute following command to make CLI more user attractive and increase developer experience:
Progress bar can be added while:
How will this change help?
It would make CLI more user attractive and increase developer experience:
Screenshots
Sample Progress Bar:
How could it be implemented/designed?
Set up the progress start and progress end between the process start
🚧 Breaking changes
No
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: