Skip to content

v3.0.3 - revert WT rpoB and remove duplicate AAs from LIMS report#46

Merged
MrTheronJ merged 10 commits into
mainfrom
smw-v303
Apr 27, 2026
Merged

v3.0.3 - revert WT rpoB and remove duplicate AAs from LIMS report#46
MrTheronJ merged 10 commits into
mainfrom
smw-v303

Conversation

@sage-wright

Copy link
Copy Markdown
Member

This PR reverts the WT rpoB change and removes duplicate AA from LIMS report.

@sage-wright sage-wright requested a review from a team as a code owner April 27, 2026 16:53
record.gene_codes["rpoB"].max_mdl_variants = [v]
processor.resolve_drug_target(record)
assert record.drug_target_value == "No mutations associated with resistance to rifampicin detected"
assert record.drug_target_value == "Predicted susceptibility to rifampicin"

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.

I think we should establish a practice for modifying existing test cases, especially as things get more complex. My first thought was to start commenting out the original assertion and link the PR/version it was changed in. That way, future us will have a clear reference for when and why it was originally updated. What do you think? Is that overkill?

f"{v.protein_change if v.protein_change != 'NA' else v.nucleotide_change}"
f"{' [synonymous]' if self._is_synonymous_rpob_rrdr(v) else ''}"
for v in gene_code.max_mdl_reportable_variants
list(set(

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.

I remember last week you brought up a good question about whether these AA's should be sorted (by position). Might be unnecessary right now, but just wanted to bring it up again. Thoughts?

Pros:

  • looks good? better than random order?

Cons:

  • might make comparing diffs more complicated

@MrTheronJ MrTheronJ merged commit 2c935c9 into main Apr 27, 2026
2 checks passed
@MrTheronJ MrTheronJ deleted the smw-v303 branch April 27, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants