You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Providing data_format: "yaml" via the standard multiqc_config.yaml is not working. However, providing the equivalent option via the CLI -k yaml is working fine. This could be a config parsing issue. This wasn't an issue in previous stable releases because we have been using this option in nf-core/viralrecon and it has worked.
So it looks like I broke this in fc65e7f when I was messing around trying to get the CLI help to look nicer. I think I added the default there so that it would show. However, that's before the config is fully loaded, so it always loads it as TSV whatever you have in other config files. Then, Click uses that default to pass it onwards and MultiQC thinks that you've set it manually on the CLI so it overwrites the actually fully parsed config. It still works with -k because that takes precedence over the Click default. Phew 😅
Description of bug
Providing
data_format: "yaml"
via the standardmultiqc_config.yaml
is not working. However, providing the equivalent option via the CLI-k yaml
is working fine. This could be a config parsing issue. This wasn't an issue in previous stable releases because we have been using this option in nf-core/viralrecon and it has worked.Steps to reproduce
✅ Via CLI
The files dumped in
multiqc_data
have theyaml
extension as expected.❌ Via Config
The files dumped in
multiqc_data
have thetxt
extension indicating that there may be an issue resolving the configuration.File that triggers the error
No response
MultiQC Error log
No response
The text was updated successfully, but these errors were encountered: