In <#C01U1E95JQ5|>, we have a param with `${projec...
# tools
d
In #C01U1E95JQ5, we have a param with
${projectDir}/assets/ncbi_genome_infos.csv
as default. This fails in linting because the
${projectDir}
is evaluated for
nextflow.config
but not for `nextflow_schema.json`:
Copy code
nextflow_config: Config default value incorrect: params.remote_genome_sources is set as ${projectDir}/assets/ncbi_genome_infos.csv in nextflow_schema.json but is /home/daluab/dev/nf-core-magmap/assets/ncbi_genome_infos.csv in nextflow.config.
Is there a way to skip this linting test? Is this a mistake in linting?
j
@Famke Bäuerle had the same question a few weeks ago and we discussed a range of options (and i picked one myself that I've implemented in mag already): https://nfcore.slack.com/archives/CE5LG7WMB/p1753350258355049
d
Thanks. A bit implicit to hide this in the code perhaps, but maybe I didn't understand this properly. I think I'll just leave out the explicit default from the schema for the time being.
j
Yeah it's not the most satisfying solution but if there might be Nextflow level solution in the future I guess it would be fine for now
👍 1
p
I think it's more something we should fix on the nf-core side to be honest.
Telling nextflow to return the config without resolving any of the config sounds difficult, if not impossible
Seeing as it's basically always just this variable, a simple find + replace in the linting code would be an easy fix I think..
(ie. infer what $projectDir absolute path is, then if it's found in the returned results of nextflow config, replace it with the var)
Bit hacky though..
j
p
Yeah, that was before I thought about it more and spoke to Ben