Skip to content

Conversation

@koji
Copy link
Contributor

@koji koji commented Oct 27, 2025

Overview

add go back function to protocol visualization page

https://opentrons.slack.com/archives/C09AFFN9N83/p1761245200385029

close AUTH-2437

Test Plan and Hands on Testing

  • open the app
  • go to the device landing page
  • select a Flex
  • go to run log
  • re-run a protocol that your app doesn't have
    check the app redirects to the protocol setup page when clicking visualization button

Changelog

Review requests

Risk assessment

low

add go back function to protocol visualization page

close AUTH-2437
@koji koji requested review from Copilot and ncdiehl11 October 27, 2025 22:41
@koji koji marked this pull request as ready for review October 27, 2025 22:41
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds navigation handling to the Protocol Visualization page to address an edge case where users attempt to access protocol visualization from the protocol setup page when re-running a protocol that doesn't exist in the app. When the protocol's analysis data is unavailable, the user is now redirected back to the previous page.

Key changes:

  • Added navigation hook to enable programmatic redirection
  • Implemented automatic back navigation when protocol analysis is missing
  • Updated dependency arrays and null checks for better React compliance

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@koji koji requested a review from jerader October 30, 2025 16:22

// this is for an edge case
// a user tries to access the visualization page from the protocol setup page by re-running the protocol
// this will be fixed in protocol visualization phase 2
Copy link
Collaborator

Choose a reason for hiding this comment

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

aren't we combining phase 1 and phase 2 now? so shouldn't we address this now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants