-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upd fix #643
Upd fix #643
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could the schema validation be changed instead to only allow a string or a 0?
E.g.
"paternal": {
"oneOf": [
{
"type": "integer",
"enum": [0]
},
{
"type": "string",
"pattern": "^(\\S+)$"
}
],
"errorMessage": "Paternal ID must be provided and cannot contain spaces. If no paternal ID is available, use 0.",
"meta": ["paternal"]
},
Seems risky having to keep track of "0" or 0.
Yeah, the neater solution would probably be to fix this is in the schema. Need to run some tests to verify |
Keep running into:
Don't think I can solve this right now, know to little about nf-schema 😅 . Would this solution be OK for now and then we try to work some more on the schema solution later? |
PR checklist
Updated createCaseChannel function to include a check for maternal and paternal ids being set to a numeric 0.
Fix for #642
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile test_one_sample,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).