Skip to content

Surface v0.5 submission fields in MultiQC plugin#13

Merged
ehsanestaji merged 1 commit into
mainfrom
feature/multiqc-adoption-polish
Jul 3, 2026
Merged

Surface v0.5 submission fields in MultiQC plugin#13
ehsanestaji merged 1 commit into
mainfrom
feature/multiqc-adoption-polish

Conversation

@ehsanestaji

Copy link
Copy Markdown
Owner

Summary

  • Preserve v0.5 submission readiness fields in the native MultiQC parser output.
  • Add MultiQC table headers for submission target/status and submission hazard counters.
  • Update MultiQC and adoption docs so the plugin surface matches the v0.5 contract.

Verification

  • Red test confirmed missing parser/header/doc behavior before implementation.
  • python3 -m unittest discover -s tests/python
  • cargo test --locked
  • git diff --check
  • Public wording scan for disallowed development-tool naming returned no matches.
  • Temporary virtualenv smoke test: multiqc --strict --module fastaguard examples/reports
  • Generated multiqc_fastaguard.txt and multiqc_data.json contain submission_target, submission_status, duplicate_first_token_id_count, and gap_like_n_run_count.

@ehsanestaji ehsanestaji merged commit b5e2572 into main Jul 3, 2026
2 checks passed
@ehsanestaji ehsanestaji deleted the feature/multiqc-adoption-polish branch July 3, 2026 17:03
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.

1 participant