-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup needed for nf-core logo / monochrome logs. #3295
Comments
Unresolved - how to fix this: tools/nf_core/pipeline-template/nextflow.config Lines 252 to 255 in 41b4516
We're not allowed We originally added it years ago to avoid filename clashes, but that's no longer needed. However, I'm not sure how to set the report directories to So we need to either:
|
using |
I don't think that tools/nf_core/pipeline-template/subworkflows/local/utils_nfcore_pipeline_pipeline/main.nf Line 35 in 45c7879
If you make a new pipeline and check this line it should be highlighted by the LSP with |
Started looking into warnings for #3294 and saw one about
monochrome_logs
being unused here:tools/nf_core/pipeline-template/subworkflows/local/utils_nfcore_pipeline_pipeline/main.nf
Line 35 in 41b4516
This seems to be a leftover from before we moved to nf-schema to print the header. The nf-core utils subworkflow no longer does this, so no longer needs the
monochrome_logs
option to be passed to it.The more I started looking into it, the more I think that there is a bit of cleanup needed here.
validation.monochromeLogs
params.monochrome_logs
def nfCoreLogo
in the nf-core subworkflow which is, as far as I'm aware, not used anywheredashedLine
function is only used bynfCoreLogo
, so can also be deleted.nextflow.config
hardcodes the logo (not using the above function), with ANSI colours hardcoded. So there is no way to disable colours.As a minimum we need to remove the unused input from the subworkflow to help solve #3294 - but we should also try to clean up this 👆🏻 so that:
--monochrome_logs
makes the nf-core logo monochromeThe text was updated successfully, but these errors were encountered: