fix(api): remove fixed trash restriction from PAPI deck conflict check #14136
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
Fixes RQA-2015
This PR removes the restriction from PAPI based deck conflict checking that prevented labware and modules from being loaded into slot 12/A3. With deck configuration, a trash does not necessarily need to be in that slot, and addressable area engine logic will prevent a trash and the deck slot it exists in from being used in the same protocol.
This change is safe to make for older protocols as well, as the newly added engine based conflict checking will prevent labware or modules from being loaded where the fixed trash labware has been automatically loaded.
Test Plan
Confirmed that the first protocol passes analysis and the second one correctly fails.
Changelog
Review requests
Risk assessment
Low.