You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following feature would be beneficial in the future:
The headers of the samplesheet should be able to be validated in strict mode, meaning if they are misspelled or missing the pipelines should throw an error instead of a warning
This behavior should be able to be turned on or off
The same feature would be nice for entries in the samplesheet, where required fields are missing.
The best solution for this is to create a new configuration option (validation.strictHeaders for example). This can then be turned on to throw errors instead of warnings for unknown headers.
Following feature would be beneficial in the future:
strict
mode, meaning if they are misspelled or missing the pipelines should throw an error instead of a warningThe same feature would be nice for entries in the samplesheet, where required fields are missing.
e.g. if following samplesheet would be present
and should be formatted like this
and either
short_reads_fastq_1
orlong_reads_fastq_1
are required fieldsThe pipeline should fail and not run empty with warnings. Also a meaningful error should be thrown in such a scenario.
It would be best this could be turned on or off in a schema_input.json.
The text was updated successfully, but these errors were encountered: