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
As you might have seen, Nextflow has recently introduced a proper language server!
Meaning that developing in Nextflow DSL-2 gives proper editor support with error highlighting, auto-completion, quick navigation through references and so on. A huge difference for the dev experience :D
It can also visualize how processes / workflows connect. Here is the Tomte workflow illustrated by the VSCode plugin (in my Peddy-WIP branch):
Tomte is currently using some syntax not supported by this plugin, such as the switch statement and for loops. Not a lot, I just needed to touch a handful places to get it error free and working.
Would it make sense to adapt the Tomte syntax to align with the syntax expected here?
The text was updated successfully, but these errors were encountered:
Good point! The addition of the nextflow language server is so nice and we should try to adhere to the standards. I think that @Lucpen also opened an issue to remove the switch logic from the pipeline, #183.
Description of feature
As you might have seen, Nextflow has recently introduced a proper language server!
Meaning that developing in Nextflow DSL-2 gives proper editor support with error highlighting, auto-completion, quick navigation through references and so on. A huge difference for the dev experience :D
https://seqera.io/blog/modernizing-nextflow-developer-experience/
It can also visualize how processes / workflows connect. Here is the Tomte workflow illustrated by the VSCode plugin (in my Peddy-WIP branch):
Tomte is currently using some syntax not supported by this plugin, such as the
switch
statement andfor
loops. Not a lot, I just needed to touch a handful places to get it error free and working.Would it make sense to adapt the Tomte syntax to align with the syntax expected here?
The text was updated successfully, but these errors were encountered: