Add support for official Nextflow parameters meta schema#113
Add support for official Nextflow parameters meta schema#113
Conversation
| private Pattern uriPattern = Pattern.compile('^#/(\\d*)?/?(.*)$') | ||
| // TODO Change the base URL once the meta schema has been officially released | ||
| final private Map<String,String> supportedCustomParameterDrafts = [ | ||
| "https://github.com/nextflow-io/schema-spec/raw/refs/heads/main/parameters_meta_schema.json": "/schemas/parameters/1.0/parameters_meta_schema.json" |
There was a problem hiding this comment.
This has to be versioned surely? main will be a moving target.
There was a problem hiding this comment.
Yes that's what the TODO statement is for :). I can't put a versioned URL there as it doesn't exist yet
mirpedrol
left a comment
mirpedrol
left a comment
There was a problem hiding this comment.
I don't see where validation.mode that you describe in the PR description is implemented. How does this work?
| ## Nested parameters | ||
|
|
||
| !!! example "New feature in v2.1.0" | ||
| !!! example "Not supported in by the official [Nextflow specifications](https://github.com/nextflow-io/schema-spec/blob/main/parameters_meta_schema.json)" |
There was a problem hiding this comment.
We could make it a warning and use admonitions so it stands out more
There was a problem hiding this comment.
Good idea! I'll update this PR fully once the schema has been released
We decided to drop this because it does basically the same as specifying your schema draft (2020-12 vs nextflow-schema) |
3 participants
This PR adds two new features:
validation.modethat can be set tolimitedto ensure compatibility with nf-core tooling, Seqera platform and othersThis PR should not be merged before a tagged version of the schema has been released