Fixes Add indents to match destination of code blocks #422

[mribeirodantas]

Signed-off-by: Marcel Ribeiro-Dantas [email protected]

[netlify[bot]]

✅ Deploy Preview for nextflow-training ready!

Name	Link
🔨 Latest commit	516f5c317f67295c17624d9a4966ad421c9294aa
🔍 Latest deploy log	https://app.netlify.com/sites/nextflow-training/deploys/675ae0e269dc12000827fd46
😎 Deploy Preview	https://deploy-preview-431--nextflow-training.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mribeirodantas]

I wonder if we shouldn't stick to nf-core conventions on code indentation, i.e.

process FOO {
    publishDir ...
    some other directive ...

    input:
    val foo
    path bar

    output:
    stdout

    script:
    """

instead of

 process FOO {

    publishDir ...
    some other directive ...

    input:
        val foo
        path bar

    output:
        stdout

    script:
    """

It's not clear to me if the way we're doing it contributes a lot to readability/understanding and if it's worth teaching people differently from how most of the community writes Nextflow pipelines.

[vdauwera]

Oh sorry to have missed this one, @mribeirodantas. I think we addressed some of this in the most recent rewrite of Hello World.

This PR is out of date so I'm going to close it, but I opened an issue to discuss/decide on a convention, and from there we can do the work to enforce it consistently.