fix(step-generation): if labware is being moved to a stacker allow stacking without a specific stackLimit
#20435
+18
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Labware definitions without a
stackLimitare not currently able to be moved to a stacker hopper. This PR checks if the stacker is in the stack list, and setsisAboveStackLimitto false. This fixes the error if a labware does not have a definedstackLimitin its definition.Test Plan and Hands on Testing
Tested on protocol in ticket EXEC-2206
Review requests
Will this mess up other labware moves?
Risk assessment
medium