-
Notifications
You must be signed in to change notification settings - Fork 587
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
Add task to ExtractCallset that verifies filter_set_name exists in GVS dataset [VS-335] #7734
Conversation
exit 1 | ||
fi | ||
>>> | ||
output { |
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.
awesome---would we ever want to re-use this code as a validation before we make the filter model to make sure the filter name doesn't already exist ?
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.
I'm hesitant to add more validation than was requested by users into individual WDLs because, I think it makes more sense, once we have one WDL to rule them all, to have an all-in-one validation step that sanity checks all the inputs before running.
Closes https://broadworkbench.atlassian.net/browse/VS-335