Fix ItemizedResource item ordering #567
Merged
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.
This PR refactors the ItemizedResource class (and its subclasses like Plate and TipRack) to store item ordering as an OrderedDict[str, str] mapping from identifier (e.g. “A1”) to child name (e.g. “plate_A1”) instead of a List[str]. This enables unambiguous conversion between indices and identifiers, resolving issues where get_item() and other methods could retrieve the wrong child due to reordered and/or extra children. The example that inspired this is a Lid as a child of Plate in front of Wells, messing up the well indexing. See #565.
Key Changes:
Why:
Previously, child retrieval methods relied on a flat list of identifiers without a stable mapping to actual child names. This was fragile in cases where there are other children (such as a Lid on a Plate). By tracking the mapping explicitly, we can safely reference children by both identifier and name without relying on implicit positional assumptions.