-
Notifications
You must be signed in to change notification settings - Fork 0
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
Prefixes for bad wdl's for validate, run or both #59
Comments
Thoughts? @seankross @tefirman |
I think I like the first approach best, followed by the second approach, not a huge fan of the third method, feels like it would be easy to forget to add a workflow to the metadata file. I also "badVal" and "badValRun" are actually the same thing, because if a workflow doesn't validate, there's no way it's going to run successfully. So I think we would just need "badVal" and "badRun". |
Thanks @tefirman Sounds good to do 1st one, but I'll wait to see what @seankross says
Okay, so we'd just have
And for tests for cromwell run we'd know to assert that a workflow prefixed with |
Exactly, WOMtool fail + Cromwell pass is not possible to my knowledge, so maybe it would just be:
|
Okay, great, so |
via @tefirman in #53 (comment)
My proposal is thus for prefixes:
badVal
badRun
badValRun
Another different take on this is to nest similar types of wdls within the same dir, and then we know the expectation from the parent dir the wdl's are in. e.g.,
A 3rd option that I kinda like is maintaining the metadata about the various WDLs in a single file, json or yaml, whatever. e.g.,
The text was updated successfully, but these errors were encountered: