-
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(shared-data, api): Add evo tips definition and restrictions on loading #16710
base: edge
Are you sure you want to change the base?
Conversation
66da179
to
c87dde7
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.
The verification logic wants to be in the engine but other than that looks good.
@@ -363,6 +372,27 @@ def ensure_definition_is_labware(definition: LabwareDefinition) -> None: | |||
) | |||
|
|||
|
|||
def ensure_labware_is_loadable( |
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 wants to be in the engine I reckon
bc3405e
to
e01dcbe
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## edge #16710 +/- ##
===========================================
- Coverage 92.43% 79.21% -13.23%
===========================================
Files 77 120 +43
Lines 1283 4533 +3250
===========================================
+ Hits 1186 3591 +2405
- Misses 97 942 +845
Flags with carried forward coverage won't be shown. Click here to find out more. |
Overview
Add evo tips definition but as a labware so that liquid handling actions can happen in the 'labware'.
Test Plan and Hands on Testing
Need to check that the stackup works as expected
Changelog
Review requests
Check that the labware role makes sense and the stacking part.
Risk assessment
Low. Adding a new labware.