fix(app): fix terminal banner render state #17240
Merged
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.
Closes RQA-3840
Overview
This PR fixes conditional logic that causes the "run succeeded" banner to render momentarily when in actuality, an error banner should render. Checking if the
commandErrorList
isnull
is not sufficient to render the success banner appropriately, because thecommandErrorList
isnull
when the network request has not yet completed. Instead, we should check if the length of the list is 0.A lower-latency solution would be to add the
/runs/:runId/commandErrors
resource to notifications, which would also simplify the conditional logic, see EXEC-1083.Current Behavior
Screen.Recording.2025-01-10.at.9.39.41.AM.mov
Fixed Behavior
Screen.Recording.2025-01-10.at.9.33.08.AM.mov
Test Plan and Hands on Testing
Changelog
Risk assessment
low - easy to validate.