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
The unit test in the WDL spec attempts to implicitly coerce a map to a struct:
version1.1structWords{
IntaIntbIntc
}
workflowmap_to_struct {
Stringa = "beware"Stringb = "key"Stringc = "lookup"output { # What are the keys to this Struct?Wordsliteral_syntax = Words {
a: 10,
b: 11,
c: 12
}
# What are the keys to this Struct?Wordsmap_coercion = {
a: 10,
b: 11,
c: 12
}
}
}
When parsing the workflow with MiniWDL's internals, while it is able to parse, the struct keys are not properly propagated (I first encountered this here).
Post parse, literal_syntax is equal to {'a': 'Int', 'b': 'Int', 'c': 'Int'} and map_coercion is equal to {'a': 'Int', 'b': 'Int', 'c': 'Int'}, instead of the expected value.
The text was updated successfully, but these errors were encountered:
The unit test in the WDL spec attempts to implicitly coerce a map to a struct:
MiniWDL currently cannot run this workflow:
When parsing the workflow with MiniWDL's internals, while it is able to parse, the struct keys are not properly propagated (I first encountered this here).
Post parse,
literal_syntax
is equal to{'a': 'Int', 'b': 'Int', 'c': 'Int'}
andmap_coercion
is equal to{'a': 'Int', 'b': 'Int', 'c': 'Int'}
, instead of the expected value.The text was updated successfully, but these errors were encountered: