-
Notifications
You must be signed in to change notification settings - Fork 178
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
feat(app): allow p1000 gen2 to fallback to specced p1000 gen1 #4316
Conversation
Codecov Report
@@ Coverage Diff @@
## release_3.14.0 #4316 +/- ##
===================================================
- Coverage 74.55% 56.27% -18.29%
===================================================
Files 120 890 +770
Lines 13763 24936 +11173
===================================================
+ Hits 10261 14032 +3771
- Misses 3502 10904 +7402
Continue to review full report at Codecov.
|
Holding until #4326 is merged |
When a robot has an attached P1000 Single GEN2, the and the uploaded protocol has a P1000 Single GEN1 attached, the app should accept the newer actual pipette as an inexact match. This mirrors the case of P300 GEN2 -> P300 GEN1 and P20 GEN2 -> P10 GEN1. re #3598
6fdbad8
to
3c7c2bc
Compare
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.
Code looks good. 👍 once tested
return false | ||
} | ||
function pipettesAreInexactMatch( | ||
protocolInstrName, |
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.
Why is this parameter untyped? It looks like it needs to know to accept string and void
When a robot has an attached P1000 Single GEN2, the and the uploaded protocol has a P1000 Single GEN1 specified, the app should accept the newer actual pipette as an inexact match. This mirrors the case of P300 GEN2 -> P300 GEN1 and P20 GEN2 -> P10 GEN1.
re #3598