From c19f69aeb18d5006cb8d2fe60ab732edeb8b24ea Mon Sep 17 00:00:00 2001
From: Simon Heumos <simon.heumos@qbic.uni-tuebingen.de>
Date: Thu, 14 Mar 2024 12:02:14 +0100
Subject: [PATCH] Update nextflow_schema.json
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
---
nextflow_schema.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/nextflow_schema.json b/nextflow_schema.json
index 225ef49d..ab4f48d7 100644
--- a/nextflow_schema.json
+++ b/nextflow_schema.json
@@ -260,7 +260,7 @@
"properties": {
"vcf_spec": {
"type": "string",
- "description": "Specify a set of VCFs to produce with --vcf_spec \"REF[:LEN][,REF[:LEN]]*\".",
+ "description": "Specify a set of VCFs to produce with `--vcf_spec \"REF[:LEN][,REF[:LEN]]*\"`.",
"help_text": "The paths matching `^REF` are used as a reference, while the sample haplotypes are derived from path names, e.g. when `DELIM=#` and with `-V chm13`, a path named HG002#1#ctg would be assigned to sample HG002 phase 1. If `LEN` is specified and greater than 0, the VCFs are decomposed, filtering sites whose max allele length is greater than `LEN`."
}
}