Example in question:

workflow my_workflow {
    take:
    data

    main:
    ch_bye = bye(hello(data))

    emit:
    ch_bye
}

workflow {
    result = my_workflow()
    result.view()
}

Note: you need to add dumy definitions of

hello()

and

bye()

, and pass some string to

my_workflow

to make it valid. Even then, it gives 2 lint warnings (unused variable and single named workflow, neither of which is true).

Stale docs are very possible and very easy. Especially whilst transitioning between two totally different language parsers that have different rules, whilst trying to keep the docs valid (and useful) for both. We try our best 😇

I'd like us to look into using an LLM or some kind of automation to check all code snippets in the docs too, longer term

We have some nice stuff for the training that @Jonathan Manning developed (where it runs all the examples and checks / updates the outputs)

I wonder if we could do something similar for the docs. Though it'll be more difficult