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

Labware V2: Accommodating Longer Labware Names in RA #3617

Closed
5 tasks
umbhau opened this issue Jun 20, 2019 · 0 comments · Fixed by #3644
Closed
5 tasks

Labware V2: Accommodating Longer Labware Names in RA #3617

umbhau opened this issue Jun 20, 2019 · 0 comments · Fixed by #3644
Labels
app Affects the `app` project bug design protocol designer Affects the `protocol-designer` project

Comments

@umbhau
Copy link

umbhau commented Jun 20, 2019

As a Run App user, I would like to be able to see full labware names when calibrating labware, so that I can clearly tell what labware I am working with.

Acceptance Criteria

  • Long labware names are handled gracefully in the calibrate sidebar (i.e. don't cause weird aligment issues)
    • User is able to see full labware name in run app calibration sidebar (e.g. in a tooltip)
  • Long labware names are handled gracefully in the calibration title bar (ie.. don't cause weird line breaks)
  • Load names should be lower_case
  • Use display name instead of load name in calibration flow side bar and title bar
@umbhau umbhau added feature Ticket is a feature request / PR introduces a feature app Affects the `app` project design labels Jun 20, 2019
@mcous mcous added bug protocol designer Affects the `protocol-designer` project and removed feature Ticket is a feature request / PR introduces a feature labels Jun 27, 2019
mcous added a commit that referenced this issue Jun 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app Affects the `app` project bug design protocol designer Affects the `protocol-designer` project
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants