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.
Currently, nf-core pipelines disallow spaces in directory paths, which unnecessarily limits usability. If users inherit datasets with spaces in the path (e.g., from external collaborators or legacy systems), they may be unable to run the pipeline without renaming files — a non-trivial operation, especially with object storage.
Nextflow stages inputs into isolated work directories, so spaces in source paths have no impact on tool execution. We continue to disallow spaces in filenames themselves to avoid downstream issues.
Allowing spaces in directory paths improves flexibility without compromising workflow robustness. Renaming paths is not always feasible (e.g., on object storage where renaming is non-atomic) and can break integrations with other systems.