Any preferences on `yaml` vs `toml` for a future N...
# pipeline-maintainers
p
Any preferences on
yaml
vs
toml
for a future Nextflow linting / auto-formatter config file? See issue. Now's the time to make your voice heard!
m
Option 3: none at all and define โ€œOne format to rule them allโ€, cfr the golang formatter, so all pipelines look the same?
shakefist 2
j
Indentation sucks, so I'm pro
.toml
Although maybe would be incosistent where we typically are using
yaml
elsewhere, right?
p
@Matthias De Smet I'd worry that people would then confuse the two formats, and wonder why the Nextflow config syntax doesn't work? Or why the two files can't be merged etc?
s
don't we have indent formatters for yaml ?
๐Ÿ‘๐Ÿป 1
p
@James Fellows Yates we're using both if you look at the full toolchain (eg. python + netlify etc). But generally yes, we use YAML or JSON for most other things already.
๐Ÿ‘ 1
s
then we stick only to yaml right ?
p
Yeah, prettier will autoformat this new autoformat config file inception
j
But indenting sucks
spaces?! Tabs!? 2 or 4?!
s
ya thats what the autoformat should take care
j
Shouldn't have to have that though for such a simple file
(but personal preference, so I'll shut up)
p
Prettier would probably run on toml as well, in fairness.
j
Sure but it's toml still less error prone
l
toml because it's probably easier to integrate into existing other config files (pyproject.toml as an example - but of course not necessarily for a nextflow formatter).
p
@Lukas Heumos you mean that we could have
[nextflow.lint]
within any root
*.toml
file in the project root?
I did wonder if we could put this stuff into an
.editorconfig
file, but I don't think that it'll work
l
IIRC most formatters have a lookup order. In the Python world, they look at
tool.toml
first, then something else, something else, then the final
pyproject.toml
.
But NF is a bit standalone so it probably wouldn't matter that much in practice
j
e
๐Ÿ˜ 1
๐Ÿ‡ช๐Ÿ‡ธ 1