Add Config for Array Indentation Spacing

[codytwinton]

I'm working with Jekyll for GitHub Pages, which uses the Ruby gem for parsing YAML. This gem prefers this spacing in Arrays:

---
simple_val: Testing 1
object_val:
  sub_object_val: Testing 2
array_val:
- Testing 3
- Testing 4

However, when auto-formatter is on, this gets converted to:

---
simple_val: Testing 1
object_val:
  sub_object_val: Testing 2
array_val:
  - Testing 3
  - Testing 4

Regardless of preference, it would be great to have an option to disable adding space indention for arrays.

[sledoux]

Hi, any plans to add this config?

[CermakM]

+1 on this one

[JPinkney]

This all depends on prettier adding this configuration or seeing if they have some api that allows to change array configuration.

[zerda]

This all depends on prettier adding this configuration or seeing if they have some api that allows to change array configuration.

And per prettier/prettier#4723, Prettier is decided to stay at do indent in mapping.

[telb99]

+1 for this, my dev teams preferred option is not to indent

[nlamirault]

+1 for this. :)

[shamil]

Also need this option

[alchemistake]

Another +1

[smyrman]

Also an issue when using kustomize edit command (See kubernetes-sigs/kustomize#1395), as it re-indents the file with similar preferences as Jekyll (removing the two additional spaces added by this plugin for an array).

This means that currently, the VS Code formatting plugin and the kustomize edit can't easily be used together.

[smyrman]

This all depends on prettier adding this configuration or seeing if they have some api that allows to change array configuration.

And per prettier/prettier#4723, Prettier is decided to stay at do indent in mapping.

Maybe a workable option could be to allow changing the formatter plugin? E.g. yamlfmt (CLI wrapper for https://sourceforge.net/projects/ruamel-yaml/)? Don't know if the exact tool is a good suggestion or not.

[sparhomenko]

Also an issue when using kustomize edit command

Same for the YAML files edited and committed by Flux v2 image-automation-controller. They've pinpointed it to the behaviour of the underlying library (kyaml) that is also used by kustomize.

yamllint has a configurable setting for sequences indentation (indent-sequences: false), so using it mitigates the problem a bit. It's just a linter though so can only be used to catch the wrong formatting after the fact.

Prettier's decision to enforce a particular style of sequence indentation is questionable to be honest. Automated tools aside, there are plenty of YAML files using non-indented sequences, particularly in the Kubernetes ecosystem.

[ludusrusso]

Same issue here +1