-
Notifications
You must be signed in to change notification settings - Fork 630
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
Add ability to provide custom defaults for publishDir directive via config file #4186
Comments
@pditommaso you closed a bunch of issues and PRs about supporting closures for these fields, so do you intend for these default settings to support closures in some way? Otherwise it isn't really addressed those other issues. In many cases they want to configure the PublishDir with task-specific inputs which requires closures. |
If the publishDir directive can be specified in the pipeline code (#4375), then you could instead use a function to provide defaults: def publishDir(path, opts=[:]) {
final defaults = [
path: params.outdir,
mode: params.publish_mode
]
defaults + [path: path] + opts
} |
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. |
This convenience is no longer needed once the workflow output DSL #4784 is implemented |
Closing in favor of the output i.e. "publish" DSL and #4839 which provides some config options for publish retry strategy |
Not 100% this should be thrown away |
This ticket aims to provide the ability to custom default settings for the
publishDir
directive via thenextflow.config
file.The default settings should be provided using the
nextflow.defaults.publishDir
configuration scope. For example:When provided, they should override the built-in default settings and applied when creating a PublishDir instance.
The text was updated successfully, but these errors were encountered: