Skip to content

fix: order secondary tables by their level order - #2

Merged
clintval merged 2 commits into
mainfrom
fix/table-order
Sep 10, 2026
Merged

clintval merged 2 commits into
mainfrom
fix/table-order

Conversation

@clintval

Copy link
Copy Markdown
Collaborator

Tables named by levels[].table came back in the order MultiQC happened to run the modules that first fed them, so in a real report a one-row cohort annotation table sat above the library table even though its level was listed last. pivot() now seeds the tables from the levels in config order and drops the ones that received no rows; tests/test_pivot.py::test_tables_follow_level_order_not_module_order covers it with a snpEff-style section running ahead of a FastQC-style one. Version bumped to 0.1.1.

Tables named by levels used to appear in the order MultiQC ran the modules
that first fed them, which put a one-row cohort table above the library
table. They now follow the order of the levels in the config, and a table
that received no rows is left out.
@clintval
clintval merged commit 9190954 into main Sep 10, 2026
5 checks passed
@clintval
clintval deleted the fix/table-order branch September 10, 2026 01:19
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