Skip to content

Conversation

@mattseddon
Copy link
Contributor

@mattseddon mattseddon commented May 1, 2023

This PR adds some code around handling errors that occur whilst we are displaying progress notifications to the user. We only need to handle these errors under the circumstances that the underlying command is not registered as a CLI command through InternalCommands.

@mattseddon mattseddon added the bug Something isn't working label May 1, 2023
@mattseddon mattseddon self-assigned this May 1, 2023
@mattseddon mattseddon force-pushed the handle-progress-error branch 2 times, most recently from 5f8f26a to 0fe982e Compare May 1, 2023 01:11
@mattseddon mattseddon force-pushed the handle-progress-error branch from 0fe982e to 1a08354 Compare May 1, 2023 01:13
@mattseddon mattseddon marked this pull request as ready for review May 1, 2023 01:13
@mattseddon mattseddon requested review from julieg18 and sroy3 as code owners May 1, 2023 01:13
@qlty-cloud-legacy
Copy link

Code Climate has analyzed commit 1a08354 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (85% is the threshold).

This pull request will bring the total coverage in the repository to 94.7% (0.1% change).

View more on Code Climate.

Copy link
Contributor

@julieg18 julieg18 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@mattseddon mattseddon merged commit d5ad8cd into main May 1, 2023
@mattseddon mattseddon deleted the handle-progress-error branch May 1, 2023 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants