-
Notifications
You must be signed in to change notification settings - Fork 179
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(protocol-designer): various select pipette bug in onboarding flow #17001
Conversation
|
looks like the editing the instruments on the overview page works a bit differently and logic seems to be working to me ⭐ |
page === 'add' && | ||
pipettesByMount[defaultMount].tiprackDefURI == null && | ||
noPipette |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for the attached screenshot case
page === 'add' && | |
pipettesByMount[defaultMount].tiprackDefURI == null && | |
noPipette | |
const isDisabled = | |
(page === 'add' && | |
pipettesByMount[defaultMount].tiprackDefURI == null && | |
noPipette) || | |
selectedValues.length === 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this results in requiring to add a 2nd pipette when you go back to add a 2nd pipette. let me look into another option
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok i think i found a way that works!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couple nits, but looks good
(page === 'add' && | ||
pipettesByMount[defaultMount].tiprackDefURI == null && | ||
noPipette) || | ||
(pipettesByMount.left.tiprackDefURI == null && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit, maybe we could add a utility to get these values rather than checking both mounts. not necessary in this PR
@@ -174,6 +166,16 @@ export function SelectPipettes(props: WizardTileProps): JSX.Element | null { | |||
} | |||
}, [location]) | |||
|
|||
const hasAPipette = | |||
(defaultMount === 'left' && pipettesByMount.right.pipetteName != null) || |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
@@ -76,7 +76,7 @@ export function SelectPipettes(props: WizardTileProps): JSX.Element | null { | |||
const allowAllTipracks = useSelector(getAllowAllTipracks) | |||
const allPipetteOptions = getAllPipetteNames('maxVolume', 'channels') | |||
const robotType = fields.robotType | |||
const defaultMount = mount ?? 'left' | |||
const defaultMount = mount |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no lol i can remove it
closes RQA-3721 RQA-3716
Overview
Fixes some bugs with the 96-channel option not showing up correctly
Fixes the copy for adding a 2nd pipette
fixes the ability to add a 2nd pipette but then proceed without completing
Test Plan and Hands on Testing
Test adding/removing/editing pipettes in the select pipette portion of the onboarding flow.
Changelog
Risk assessment
low