fix(app): filter qt out of recent runs to show emptyruns tate #16167
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.
fix RQA-3130
Overview
If all previous runs are quick transfer runs, the runs were getting filtered out but the empty run state was not displaying. We need to do the run filtration at a higher level to properly show an empty run history on both ODD and desktop
Test Plan and Hands on Testing
On a robot with no run history, run a quick transfer. See that the run dashboard still shows no run history. Ensure that the run dashboard still appears as expected for robots with non-quick transfer runs
Changelog
RecentProtocolRuns
on desktop, use a filtered runs list throughout the file instead of returning a null list item for quick transfer runsrecentRunsOfUniqueProtocols
listReview requests
Look over code changes
Risk assessment
Low-Med, we should test that adding a query for protocols at the top level of the RobotDashboard doesn't visibly increase loading time