Run App: User Settings

[umbhau]

As a user, I would like access to settings for my Robot and Run App.

Acceptance Criteria

• User can view 'Advanced Settings' section on Robot Settings page
• User can view 'Advanced Settings' section on App Settings page
• User can toggle robot-level feature flags in the Robot 'Advanced Settings' section
• User can toggle app-level feature flags in the App 'Advanced Settings' section

Design

Zeplin > Run App Screens > 'Advanced Settings' tab

[pantslakz]

hello @btmorr can you flesh out which features flags need to show under robot, and which need to show under app?

[mcous]

@pantslakz for the moment, the only one we need for app is:

• Show dev tools (requires restart)

[pantslakz]

@mcous when user flicks this on - what do they see in the app? Do we require additional UI within the app to represent these dev tools?

[mcous]

@pantslakz, no, this just switches on the normal Chrome/Electron devtools. This is the same option that is automatically enabled when you run the application in development mode from source, so no additional UI is required

[pantslakz]

from ben:
https://github.com/Opentrons/opentrons/blob/edge/api/opentrons/config/feature_flags.py

[btmorr]

This looks fantastic. For the record, @pantslakz and I talked f2f, and the server is going to report a list of settings to expose through this panel in roughly the form:

{
  "settings": [
    {
      "title": "Calibrate to bottom of well",
      "description": "Perform labware calibration by moving the tip to the bottom-center of the well rather than the top-center (which is the default if this option is unset)",
      "value": true
    },
    {
      "title": "Other setting",
      "description": "Long description of next setting",
      "value": false
    }
  ]
}

@mcous do you have any thoughts/requests?

[mcous]

That response schema looks perfect

[btmorr]

Ticket for the backend work: #1656

[mcous]

JK still need to do robot settings

[umbhau]

@btmorr linking a ticket for blocker.