Skip to content

Y26-125 dual index tags update in mlwh#5745

Open
andrewsparkes wants to merge 5 commits intodevelopfrom
Y26-125-dual-index-tags-update-in-mlwh
Open

Y26-125 dual index tags update in mlwh#5745
andrewsparkes wants to merge 5 commits intodevelopfrom
Y26-125-dual-index-tags-update-in-mlwh

Conversation

@andrewsparkes
Copy link
Copy Markdown
Member

Closes #5677

Changes proposed in this pull request

@codecov
Copy link
Copy Markdown

codecov Bot commented May 1, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.31%. Comparing base (7bcf30f) to head (f52f6d5).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #5745   +/-   ##
========================================
  Coverage    87.30%   87.31%           
========================================
  Files         1476     1476           
  Lines        33517    33510    -7     
  Branches      3549     3553    +4     
========================================
- Hits         29263    29258    -5     
+ Misses        4233     4231    -2     
  Partials        21       21           
Flag Coverage Δ
javascript 50.00% <ø> (ø)
ruby 87.33% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Copy Markdown
Contributor

@StephenHulme StephenHulme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might benefit from someone more familiar with aliquots, but looks good to me.

# NB. the asset here is a well, and the well_has_single_aliquot? validation ensures there is only one aliquot
# NB. we are fetching via row so this is the same aliquot instance so saved_changes? works to detect
# substitutions
row.aliquots.first.assign_attributes(tag:, tag2:)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
row.aliquots.first.assign_attributes(tag:, tag2:)
aliquots.first.assign_attributes(tag:, tag2:)

I think we don't need the row passed through. If you look at the code for the other types of library manifest, they reference aliquots directly (which is delegated to asset on the base class) - so should work to do the same here.


Equivalent classes for other manifests:

  • app/sequencescape_excel/sequencescape_excel/specialised_field/i7.rb > app/sample_manifest_excel/sample_manifest_excel/tags/aliquot_updater.rb
  • app/sequencescape_excel/sequencescape_excel/specialised_field/tag_index.rb


def tag_group_id
@tag_group_id ||= ::TagGroup.find_by(id: dual_index_tag_set.tag_group_id, visible: true).id
# defensive guard to avoid NoMethodError being thrown when dual_index_tag_set is nil, caught by validation
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Think the comment states the obvious 😃
Great to have fixed the bug at the same time as this story 🙌

Copy link
Copy Markdown
Contributor

@KatyTaylor KatyTaylor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, except I think you can take the row-related changes out, to simplify even more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

3 participants