We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
meta
parameter_meta
I have run in to a case with our documentation where miniwdl flags a trailing comma in an array in a meta or parameter_meta section as problematic.
miniwdl
array
For example:
version 1.1 task foo { parameter_meta { bar: { suggestions: [1,2,3,], help: "bar", default: 1, } } input { Array[Int] bar = [1,2,3,] } command <<< >>> }
Yields:
% miniwdl check tools/test.wdl (tools/test.wdl Ln 6 Col 33) Unexpected token Token('STRING1_FRAGMENT', '],\n help: "bar",\n default: 1,\n }\n }\n input {\n Array[Int] bar = [1,2,3,]\n }\n \n command <<< >>>\n}\n') at line 6, column 33. Expected one of: * FALSE * SIGNED_FLOAT * LBRACE * NONE * TRUE * FLOAT * ESCAPED_STRING * LSQB * INT * SIGNED_INT * ESCAPED_STRING1 Previous tokens: [Token('COMMA', ',')] suggestions: [1,2,3,],
I don't see this as being disallowed by the spec. I will note that the trailing comma is accepted for declarations.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I have run in to a case with our documentation where
miniwdl
flags a trailing comma in anarray
in ameta
orparameter_meta
section as problematic.For example:
Yields:
I don't see this as being disallowed by the spec. I will note that the trailing comma is accepted for declarations.
The text was updated successfully, but these errors were encountered: