Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(app): prevent "run again" banner from rendering after navigating away from the current run #14973

Merged
merged 1 commit into from
Apr 22, 2024

Conversation

mjhuff
Copy link
Contributor

@mjhuff mjhuff commented Apr 22, 2024

Closes RQA-2620

Overview

This PR fixes the "run successful" banner, so it only displays for the current run.

There are a few minor refactors included as well. ProtocolRunHeader needs some serious refactoring, and I've added a TODO and made a ticket for it.

Current Behavior

Screen.Recording.2024-04-22.at.8.36.10.AM.mov

Fixed Behavior

Screen.Recording.2024-04-22.at.8.40.00.AM.mov

Test Plan

  • Follow the videos as guides.

Changelog

  • The "run successful" banner now displays on the current run only.

Risk assessment

low

@mjhuff mjhuff requested review from a team April 22, 2024 14:51
@mjhuff mjhuff requested a review from a team as a code owner April 22, 2024 14:51
@mjhuff mjhuff requested review from brenthagen and removed request for a team and brenthagen April 22, 2024 14:51
@@ -570,6 +567,7 @@ interface ActionButtonProps {
isResetRunLoadingRef: React.MutableRefObject<boolean>
}

// TODO(jh, 04-22-2024): Refactor switch cases into separate factories to increase readability and testability.
Copy link
Contributor

Choose a reason for hiding this comment

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

👍

Copy link
Contributor

@koji koji left a comment

Choose a reason for hiding this comment

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

lgtm
thank you for fixing this!

@mjhuff mjhuff merged commit 2532997 into edge Apr 22, 2024
20 checks passed
@mjhuff mjhuff deleted the app_fix-success-banner-rendering branch April 22, 2024 18:24
y3rsh added a commit that referenced this pull request Apr 23, 2024
* edge: (194 commits)
  fix(app): clone run with RTPs from HistoricalProtocolRun (#14959)
  fix(api): Filter out `air_gap()` calls as higher-order commands (#14985)
  fix(app): fix infinitely re-rendering/never rendering firmware success toasts (#14981)
  feat(api): add option to ignore different tip presence states (#14980)
  feat(opentrons-ai-client) add input textbox to container (#14968)
  fix(app): add robotSerialNumber to proceedToRun event (#14976)
  fix(api): remove homing patch fix for right mount when a 96-channel is attached (#14975)
  feat(api-client,app,react-api-client): upload splash logo from desktop app (#14941)
  fix(robot-server): notify /runs when a non-current run is deleted (#14974)
  feature(api, robot-server): Allow fixit commands to recover from an error (#14908)
  feat(hardware-testing): enable multi sensor processing in liquid probe (#14883)
  fix(app): prevent "run again" banner from rendering after navigating away from the current run (#14973)
  refactor(components): refactor roundtab stories (#14956)
  refactor(protocol-designer): assign module slot in createFileWizard instead of modal (#14951)
  fix(app, api-client): fix choose protocol slideout issue (#14949)
  refactor(protocol-designer): tip position modal max values round down (#14972)
  feat(app): add tiprack selection step to quick transfer flow (#14950)
  ci(shared-data): install dependencies in workflow (#14958)
  fix(components): fix icon stories (#14969)
  feat(opentrons-ai-client): introduce react-markdown to chat display component (#14965)
  ...
Carlos-fernandez pushed a commit that referenced this pull request May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants