-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show both parent and child relationships on Labware #1641
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #1641 +/- ##
===========================================
- Coverage 74.95% 74.90% -0.06%
===========================================
Files 420 420
Lines 14300 14297 -3
===========================================
- Hits 10719 10709 -10
- Misses 3581 3588 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I don't know the logic well enough to comment on the validity of it, but nothing jumps out as bad. Nice work!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great but can we please test it for something where there are a LOT of parents. e.g. in Bioscan the LBSN-384 PCR 2 Pool tube will have 24 parent 384-well plates.
e.g. in Cardinal the LCA Blood Array plate could have 24 parent tubes
e.g. in scRNA Core the LRC Blood Bank could have many parent tubes
Good point @andrewsparkes, here's the updated screenshot for a And here's one for the children on a |
Was this one paused because it broke the integration suite selenium tests? Or was that another one? I would advocate for merging this in if we're happy it works well. |
Yes, that's right. Integration suite broke quite badly because it was relying on the undelying If there is value in fixing IntSuite to try find and parse the barcode names/links themselves, then I'm happy to look at this again. |
I think there's a lot of value in this PR. Is there an issue in the backlog for this? If not, we could make one and put it forward for prioritisation? Just so that work is tracked, as it may not be trivial! |
This reverts commit e0ac9d5.
Showing a pooled-tube as a parent is tricky as the correct presenter needs to be used.
Updated and ready for review, Integration Suite changes can be found here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works well 👌
Code Climate has analyzed commit 94d3402 and detected 2 issues on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 55.5% (50% is the threshold). This pull request will bring the total coverage in the repository to 91.1% (0.0% change). View more on Code Climate. |
Closes a long outstanding bug-bear.
Possibly improves #645.
Dependent on sanger/General-Backlog-Items#405
Changes proposed in this pull request
data-plate-view
attributeHere is a good example in UAT
Before:
After:
Instructions for Reviewers
See https://gitlab.internal.sanger.ac.uk/psd/integration-suite/-/merge_requests/154 for Integration Suite changes
[All PRs] - Confirm PR template filled
[Feature Branches] - Review code
[Production Merges to
main
]- Check story numbers included
- Check for debug code
- Check version