A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

I dislike the spacing of import statements:
```include { MULTIQC                                   } from '../modules/nf-core/multiqc/main'
include { paramsSummaryMap                          } from 'plugin/nf-schema'```
please dont shoot me

But really it should be:
```include { MULTIQC          } from '../modules/nf-core/multiqc/main'
include { paramsSummaryMap } from 'plugin/nf-schema'```
And its more readable imo than:
```include { MULTIQC } from '../modules/nf-core/multiqc/main'
include { paramsSummaryMap } from 'plugin/nf-schema'```

This is a very confusing thread to read on mobile :sweat_smile:

Slack could really use an option to disable wrapping on code blocks

I have auto format on save that put everything as Arthur showed

What I didnt show was a bunch of other imports that force that crazy style of spacing. I prefer what Arthur mentioned:
```include { MULTIQC } from '../modules/nf-core/multiqc/main'
include { paramsSummaryMap } from 'plugin/nf-schema'```
Is optimal imo.

I don't care much for all the space to be honest, and I'd rather see the `}` nicely align.
:meow_love: Harshil Alignment forever :meow_love:
But I see your point.

Out of interest why is the alignment of the ending `}` important to you?

Aligning the `}` makes it much easier to see what’s being imported at a glance imo

Visually, it unclutters the line and the filepath is generally much less relevant to me

This to me makes more visual sense but I might be crazy:
```include { MULTIQC }                                   from '../modules/nf-core/multiqc/main'
include { paramsSummaryMap }                          from 'plugin/nf-schema'```

It also has the benefit of aligning the filepaths and that does allow one to quickly scan and see what is from the modules vs subworklows, local vs nf-core

Braces are ugly, the further they are from my vision the better

you can break up the section into some shorter and some longer imports though