user
01/26/2026, 1:59 PM{
"$schema": "<https://json-schema.org/draft/2020-12/schema>",
"$id": "<https://raw.githubusercontent.com///nextflow_schema.seqera.json>",
"title": "Lorem ipsum",
"type": "object",
"definitions": {
"config_part_1": {
"title": "Config part 1",
"type": "object",
"properties": {
"prop_1": {
"type": "string",
"default": "foo"
},
"prop_2": {
"type": "string",
"default": "bar"
},
"dataset_1": {
"type": "string",
"format": "file-path",
"mimetype": "text/csv"
}
}
},
"config_part_2": {
"title": "Config part 2",
"type": "object",
"properties": {
"prop_3": {
"type": "integer",
"default": 5
},
"prop_4": {
"type": "number",
"default": 0.8
}
}
}
},
"properties": {},
"allOf": [
{
"$ref": "#/definitions/config_part_1"
},
{
"$ref": "#/definitions/config_part_2"
}
]
}
I've validated the schema using
% npx ajv-cli validate \
--spec=draft2020 \
-s schema.json \
-d /dev/null \
--strict=false
unknown format "file-path" ignored in schema at path "#/definitions/config_part_1/properties/dataset_1"
unknown format "file-path" ignored in schema at path "#/definitions/config_part_1/properties/dataset_1"
/dev/null valid
It warns about the "file-path" format, but that's the format to use when loading datasets in Seqera if I'm not mistaken, so that should not be the problem, no?Phil Ewels
01/26/2026, 2:46 PMPhil Ewels
01/26/2026, 2:46 PMPhil Ewels
01/26/2026, 2:47 PMnf-core pipelines schema build for working with schema JSON files as it creates it all via a GUI and should give valid JSON. It works for any piepline, not just nf-corePhil Ewels
01/26/2026, 2:47 PMPhil Ewels
01/26/2026, 2:49 PMPhil Ewels
01/26/2026, 2:49 PMPhil Ewels
01/26/2026, 2:49 PMuser
01/26/2026, 3:00 PMuser
01/26/2026, 3:02 PMPhil Ewels
01/26/2026, 3:40 PMdefs versus definitions thing, that changed between JSON schema versionsPhil Ewels
01/26/2026, 3:40 PMuser
01/27/2026, 7:23 AMdefs worked. thanks!Phil Ewels
01/27/2026, 8:26 AM