forked from nf-core/rnaseq
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Refactor ext config as process inputs #1
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ben Sherman <[email protected]>
|
Closing, follow nf-core/fetchngs#312 for latest developments |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR demonstrates how to remove the module configs by refactoring ext config settings into process inputs.
the module config is only used to define process config, specifically
ext
andpublishDir
this process config could be in the process definition, but isn't because it's usually pipeline-specific rather than inherent to the generic module. it is also useful to overwrite settings e.g. for different subworkflows that call the same process
the upcoming workflow publish definition (Workflow output definition nextflow-io/nextflow#4784) replaces
publishDir
with a newpublish
definition in the Nextflow DSL, so now the only purpose of the module config is to provideext
config to processesext
config is essentially a shortcut for pipeline parameters, while it is convenient, it makes the pipeline harder to understand overall as the "inputs" to a process are split between pipeline code, params, and configthis PR shows how these
ext
config settings can be refactored as process inputs. configurability can be preserved by providing the same ext settings as pipeline params. it makes the params longer, but it is a more transparent and comprehensive view of what the pipeline "inputs" areit is in line with the push to use params only in the top-level workflow and pass params as inputs to subworkflows and processes, in order to increase the modularity of the pipeline