-
Notifications
You must be signed in to change notification settings - Fork 664
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
Better handle error reporting for syntax errors #3325
Comments
See also #2082 |
I encountered a similar syntax issue when using the "take" and "emit" parameters in the DSL2 syntax My incorrect code snippet for the workflow was
... and this gave the When I corrected the workflow by putting each "take" and "emit" parameter on their own lines, it resolved the issue, though the error message did not really indicate that was the underlying problem.
(Off-topic, but the "Workflow" section of the "DSL2" documentation here does not give any examples of how to use "take" and "emit" for 2+ samples, so I had to do trial and error to figure that out) |
Hi @adkinsrs , I think you can specify multiple channels in a single take / emit, you just don't need to separate them with a comma. |
@bentsherman thanks for the heads up on that. I am still stumbling a bit with the syntax... when to use commas, colons, etc. and when not to. UPDATE: Found out it works as
and not |
Note that using syntax highlighting at least helps a little here: process foo {
debug true:
input: path x,
"""
echo "foo ${task..index} ${task.workDir}"
"""
}
workflow {
foo()
} |
Bug report
When there's an in valid syntax the reported is intelligible. for example:
The text was updated successfully, but these errors were encountered: