-
Notifications
You must be signed in to change notification settings - Fork 180
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): oDD labware setup map migration to using baseDeck #13858
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## edge #13858 +/- ##
=======================================
Coverage 70.85% 70.85%
=======================================
Files 2496 2497 +1
Lines 70198 70225 +27
Branches 8568 8576 +8
=======================================
+ Hits 49736 49761 +25
- Misses 18381 18382 +1
- Partials 2081 2082 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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 deck map LGTM !
labwareLocations: mockLabwareLocations, | ||
moduleLocations: mockModuleLocations, | ||
}) | ||
.mockReturnValue(<div>mock base deck</div>) |
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.
not critical, a simple way to test the component logic would be to render something from mockProtocolModuleInfo
in this base deck mock
closes RAUT-822
Overview
Splits the modal into its own component and then updates the map render to use base deck.
Test Plan
Upload a protocol to the ODD and look at labware setup map view. See that the deck rendering correctly and clicking on the labware opens the correct labware details modal.
Changelog
baseDeck
to haveonLabwareClick
propLabwareMapViewModal
and create testProtocolSetupLabware
Review requests
see test plan
Risk assessment
low