Closed TCLamnidis closed 8 months ago
This is a known bug that has already been fixed in MultiQC 1.15, and would be fixed within eager by bumping MQC versions.
1.15
Adding this issue to better document that this specific frustrating behaviour is fixed in the upcoming release (2.5.0) CHANGELOG.md.
2.5.0
This is a known bug that has already been fixed in MultiQC
1.15
, and would be fixed within eager by bumping MQC versions.Adding this issue to better document that this specific frustrating behaviour is fixed in the upcoming release (
2.5.0
) CHANGELOG.md.