Separate the store directory from the filename in the trace, dag, report, and timeline scopes

[mahesh-panchal]

New feature

It would be nice if the configuration scopes report, trace, dag, and timeline had separate
settings to control the directory they're stored in and separately what to name the file.

report {
    enabled = true
    directory = "${params.outdir}/pipeline_info"
    filename = "report.html"
    overwrite = true
}

Or perhaps have this also somehow linked with the new publishing syntax too since it feels like it should be related in some way.
E.g. rather than a config scope, have a function or something special that's limited in where it can be placed which can be set by the publishing syntax.

workflow {
    ...
 
    publish:
    workflow.dag()      >> 'pipeline_info/'
    workflow.report()   >> 'pipeline_info/'
    workflow.timeline() >> 'pipeline_info/'
    workflow.trace()    >> 'pipeline_info/'
}

Usage scenario

I would like to not change the filename ( and have the timestamp and session_id ), but only update where I want to store
the reports.

Suggest implementation

(Highlight the main building blocks of a possible implementation and/or related components)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[bentsherman]

I wonder if a good solution would be the following rule: if outputDir is defined and the report file is a relative path, it will be automatically resolved against outputDir

[mahesh-panchal]

But often, output folders, if supplied, can be relative too. Nextflow would then resolve the relative path against the outputdir instead of the current directory.

I personally think it's not a big problem, but this may be an additional cognitive load for some who struggle with paths.

[nvnieuwk]

I wonder if a good solution would be the following rule: if outputDir is defined and the report file is a relative path, it will be automatically resolved against outputDir

I like this! I'm all for uniformity in this case and it would make the most sense

[znorgaard]

I wonder if a good solution would be the following rule: if outputDir is defined and the report file is a relative path, it will be automatically resolved against outputDir

Agreeing with @nvnieuwk. I also like this option.

[bentsherman]

See #6812 for the solution we are currently considering

[mahesh-panchal]

But if I understand it correctly it doesn't solve the original issue which is that I would like to simply supply the directory, and keep the default file name, (which includes the timestamp).

[bentsherman]

I think for that you just need to be able to reference the timestamp that Nextflow uses, or just create your own like the nf-core pipeline template