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
Is your feature request related to a problem? Please describe.
When performing multiple parallel tasks, it's likely that some of them may fail without stopping the entire process. It would be nice if there was a way to signal to the user that a task has failed.
Describe the solution you'd like
Currently, ProgressTask exposes a method called StopTask(). The least intrusive solution I see is to add an overload called StopTask(bool isError).
If the task is stopped with an error, we can apply some kind of ErrorStyle, which would make the progress bar appear red. Additionally, we can make it so a failed task displays an X in the PercentageColumn.
Describe alternatives you've considered
I considered writing something to the console myself, but it breaks the progress reporting.
Additional context
Here's how it currently looks:
One of the tasks has failed, but its progress remains at 0 with no visual indication that it crashed. As a user, it's not clear whether it's just stuck at 0% or failed.
Please upvote 👍 this issue if you are interested in it.
The text was updated successfully, but these errors were encountered:
@patriksvensson would you take a PR for this? I was thinking of adding bool Failed { get; set;} to the ProgressTask and an additional property (Style FailedStyle {get;set;} = Color.Red?) to the ProgressBarColumn
Edit: oups. I see there's already a PR open for something similar
Is your feature request related to a problem? Please describe.
When performing multiple parallel tasks, it's likely that some of them may fail without stopping the entire process. It would be nice if there was a way to signal to the user that a task has failed.
Describe the solution you'd like
Currently,
ProgressTask
exposes a method calledStopTask()
. The least intrusive solution I see is to add an overload calledStopTask(bool isError)
.If the task is stopped with an error, we can apply some kind of
ErrorStyle
, which would make the progress bar appear red. Additionally, we can make it so a failed task displays anX
in thePercentageColumn
.Describe alternatives you've considered
I considered writing something to the console myself, but it breaks the progress reporting.
Additional context
Here's how it currently looks:
One of the tasks has failed, but its progress remains at 0 with no visual indication that it crashed. As a user, it's not clear whether it's just stuck at 0% or failed.
Please upvote 👍 this issue if you are interested in it.
The text was updated successfully, but these errors were encountered: