fix(app): fix back to back manual move commands on desktop app #17129
+34
−1
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.
Closes RQA-3728
Overview
Since the introduction of the move labware intervention deck map, chaining back to back move interventions has posed a challenge, see comments in #13005.
The
setTimeout
solution proposed in the linked PR effectively worked, and this code looks like it got dropped at some point. However, there are other ways of doing the same thing that are more React Spring-esque, using the API'sreset
property.Current Behavior
2024-12-02_14-00-55.mp4
Fixed Behavior
Screen.Recording.2024-12-17.at.3.10.46.PM.mov
Test Plan and Hands on Testing
Changelog
Risk assessment
low