-
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
feat(shared-data): add deck schema v6 #17250
base: edge
Are you sure you want to change the base?
Conversation
This schema contains a concept of "locating features" for addressable areas. These locating features are things that constrain the position of labware loaded on top of the addressable area. The presence of a locating feature indicates that the addressable area can contain deck items. Which locating feature is available constrains which labware can be loaded; different labware define different locatable features (for instance, their back left or front left corners, or the outer surface of one of their wells). Locating feature names are not constrained to enums because we expect a fairly wide number of them. Closes EXEC-80
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.
Looks great so far. Very excited for this.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## edge #17250 +/- ##
==========================================
+ Coverage 73.84% 74.04% +0.20%
==========================================
Files 43 43
Lines 3303 3329 +26
==========================================
+ Hits 2439 2465 +26
Misses 864 864
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Remove the duplicate entry for v4 and add the missing entries for v5 and v6. This appears unused, but we may as well correct it.
This has a matingSurfaceUnitVector field, which does not exist in schema 6. Rename the type so it doesn't look more generally usable than it actually is.
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.
Looks good so far, other than whatever modules are missing.
This schema contains a concept of "locating features" for addressable areas. These locating features are things that constrain the position of labware loaded on top of the addressable area. The presence of a locating feature indicates that the addressable area can contain deck items. Which locating feature is available constrains which labware can be loaded; different labware define different locatable features (for instance, their back left or front left corners, or the outer surface of one of their wells).
Locating feature names are not constrained to enums because we expect a fairly wide number of them.
To come out of draft
risk
low, because nothing should be using this (purposeful, will be followup prs)
Closes EXEC-80