You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature or problem you’d like to solve
Currently, the CLI doesn't show a progress status.
This leads to misunderstandings in its usage. We need to indicate the progress of the dependencies being processed (either in parallel - like now happens - or not).
Proposed solution
I would keep the way we process dependencies right now, in parallel (for performance reasons).
At the same time, I and @fntlnz propose to update a progress counter while processing the dependencies and show it in the terminal.
The progress counter can be stored in the context.Context we pass along by using the mechanism already in place. In fact, the listen.BulkPackages already takes in an option to inject such a context.
If we want we can also store the total number of dependencies (per type), by using the same context.Context mechanism (even tho this is not necessary because we have the total in the place where we'll be actually doing the progress visualization).
Roughly, what I propose is:
we create an (integer?) variable to track the progress when the root command boots up
we store it in the context
we update the (integer?) variable value in the internal listen.BulkPackages callback
we visualize the progress (in the command implementation) by concurrently reading this variable value
Additional context
NONE
The text was updated successfully, but these errors were encountered:
Describe the feature or problem you’d like to solve
Currently, the CLI doesn't show a progress status.
This leads to misunderstandings in its usage. We need to indicate the progress of the dependencies being processed (either in parallel - like now happens - or not).
Proposed solution
I would keep the way we process dependencies right now, in parallel (for performance reasons).
At the same time, I and @fntlnz propose to update a progress counter while processing the dependencies and show it in the terminal.
The progress counter can be stored in the
context.Context
we pass along by using the mechanism already in place. In fact, thelisten.BulkPackages
already takes in an option to inject such a context.If we want we can also store the total number of dependencies (per type), by using the same
context.Context
mechanism (even tho this is not necessary because we have the total in the place where we'll be actually doing the progress visualization).Roughly, what I propose is:
listen.BulkPackages
callbackAdditional context
NONE
The text was updated successfully, but these errors were encountered: