feat: added progress indicator at the start of create #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a progress indicator to the eksup CLI tool to provide users with a
better understanding of the progress of the analyze and create operations. We are
using the indicatif crate to implement the progress indicator. Here is a summary of
the changes and considerations:
A new ProgressTracker struct is implemented in a separate progress.rs module. This
struct handles creating and updating the progress bar based on the percentage of
progress made.
The progress tracker is initialized at the beginning of the analyze and create
functions. It is updated at significant milestones within the functions using the
set_progress() method.
The progress bar relies on an approximate progress percentage rather than a fixed
number of tasks. This approach allows for greater flexibility, but may be less
precise than having a predetermined number of tasks. Be sure to adjust the progress
updates in the code based on a good understanding of the overall process.
Motivation
clowdhaus#14
Resolves #
clowdhaus#14
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.