Request: Make MultiQC 1.24.1+galaxy0 custom parsing backwards compatible with 1.11+galaxy1

[jennaj]

The updated version of MultiQC toolshed.g2.bx.psu.edu/repos/iuc/multiqc/multiqc/1.24.1+galaxy0 has trouble parsing certain data lines into a custom content table, specifically any that start with a hash # character.

The prior version of MultiQC toolshed.g2.bx.psu.edu/repos/iuc/multiqc/multiqc/1.11+galaxy1 was able to ignore those hash # lines during processing. Meaning, those values did not trigger a failure, and were not displayed in the final output HTML table either.

I can't tell if this change is inside MultiQC itself or the Galaxy wrapper. MultiQC did seem to make changes to support more custom plot types .. maybe a hash is now a reserved character, or the yaml content checks are stricter?

Test history with full details: https://usegalaxy.eu/u/jenj/h/bug-quast-tabular-report-into-multiqc-custom-table

Reported at: https://help.galaxyproject.org/t/updated-version-of-multiqc-1-24-1-galaxy0/13431

Workaround for Galaxy end-users

• Symptom: trouble parsing certain data lines into a custom output.
• What to do: inspect the input file format and try to simplify.
• Is a particular line or file the problem? find clues in your job logs! click into the i-icon and review.
• A guide is available here: https://multiqc.info/docs/custom_content/