-
Notifications
You must be signed in to change notification settings - Fork 186
fix(app): allow setup with no pipette #19160
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
base: chore_release-8.6.0
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## chore_release-8.6.0 #19160 +/- ##
=======================================================
+ Coverage 24.00% 24.19% +0.18%
=======================================================
Files 3377 3377
Lines 296968 297021 +53
Branches 31523 31541 +18
=======================================================
+ Hits 71301 71870 +569
+ Misses 225649 225128 -521
- Partials 18 23 +5
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
export function useModuleAttachedToast( | ||
launchModuleSetupCallback: () => void | ||
): void { | ||
const newModules = useGetNewModules() | ||
const currentlySetuppableModules = useGetModulesNeedingSetupThatCanCurrentlyBeSetUp() |
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.
“setuppable” 😅
// allNeedingSetup is a superset of allSetupable | ||
const hasUnsetupabbleModules = allNeedingSetup.length > allSetupable.length | ||
const isSingleModule = newModules.length === 1 && !hasUnsetupabbleModules | ||
const shortCircuitFlow = attachedModuleOnLaunch != null || isSingleModule |
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.
Can you add another comment explaining this variable a bit?
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.
Thanks for fixing! I didn’t test it out but code lgtm.
We want to allow module setup flows when there aren't pipettes attached, if the module can be setup without pipettes. Which is some of them, some of the time, from 3 different places. "Closes" RQA-4481
This is a little nicer. Split up the getNewModules code to separate modules between whether or not they need a pipette to be set up, so we can prompt for modules that can be set up immediately.
Sorry! It's kind of ugly but needed, right now
This way you won't be confused if you only see your stackers
0688d87
to
0479406
Compare
We want to allow module setup flows when there aren't pipettes attached, if the module can be setup without pipettes. Which is some of them, some of the time, from 3 different places.
Closes RQA-4481
The new behavior applies to stackers and to absorbance readers, since neither requires a pipette for setup.
The new behavior should be: