`nextflow config` without resolving variables

[ewels]

We use nextflow config to build and lint schema files in @nf_core. However, if a parameter contains $projectDir or similar, Nextflow resolves the local path. This is unhelpful when working with the schema, where we want the string representation of the parameter.

It'd be useful to have a flag for this command that prevents the resolution of parameter variables.

This may also come into play for Nextflow itself when we start interacting with the schema more directly.

[bentsherman]

Why don't you just take the output of nextflow config and replace the resolved projectDir with $projectDir ?

[ewels]

Because there could be many other variables / params, $projectDir was just the example that came up.

[bentsherman]

I think that would be going outside the purpose of nextflow config which is to evaluate the config as much as possible, not to reproduce the source code