Chris Llanwarne
Chris Llanwarne
If we want to put rich information in there, we should allow >1 line of text. We could maybe re-use the triple-angle brackets style, eg: ```wdl workflow foo { meta...
One thought I'd had on making imports a bit more intuitive is to allow an optional `namespace` field at the top of a WDL file like this: ```wdl version 1.X...
### Today: ```wdl call foo { input: x = x_in, y = y_in } ``` ### Proposal: ```wdl call foo { x = x_in, y = y_in } ``` ###...
To make life easier for authors doing string checks like in https://gatkforums.broadinstitute.org/wdl/discussion/10354/multiple-backends-for-cromwell#latest Eg: ``` File f Boolean a = endsWith(basename(f), ".suffix") Boolean b = startsWith(basename(f), "prefix.") Boolean c = contains(basename(f),...
As mentioned a couple of times, the pair dereferencing is not intuitive (you have to look it up in the docs to be able to find it). Perhaps we could...
I think most people would expect this (https://github.com/broadinstitute/cromwell/issues/3384) to work, but it's probably worth making that explicit in the SPEC. Draft implementation: https://github.com/openwdl/wdl/tree/199-short-circuit
Seems like an obvious extension to having `structs` and `parameter_meta` sections, eg: ```wdl struct foo { File f Int i parameter_meta { f: "A file containing a set of important...
NB this is *not* about WDL 1.0 vs draft-2 etc. It's about versioning of WDL files within a repo. As I understand things, TRS repos (amongst others) will allow people...
I wonder whether this would be a great idea or a terrible one... A lot of languages allow implied types (ie the language is strongly typed but the author doesn't...
OpenAPI allows one to generate stub clients relatively easily. As a WES consumer, it would be fantastic to be able to import a WES client from an official source. It...