The first example should not be affected as that are types not an object.

If you consider I misinterpret it ("must be" vs "should be") please dismiss the review.
Then I will just override this in my personal projects 😅

Now I'm confused, is this to enforce this?

const { width, height } = getSize()

or this ?

const { 
  width,
  height
} = getSize()

AFAIK, the first one is the traditional Nextcloud code style, right?

traditional Nextcloud code style

define this please ^^

In PHP currently the style is going to the second one. In fronend I see both.
The documentation recommends the second style.
I personally also prefer one element per line due to readability.

But to be honest if this needs already this discussion here, then we have not agreed on one style and thus need to first agree upon one and until then allow both.

traditional Nextcloud code style

define this please ^^

No hardcoded rules, I guess this is just old habit from most of the old devs.
It seems like I've seen more one-liners than split lines 🤷
Cannot confirm this is true or not, just a feeling 🙈

The first example should not be affected as that are types not an object.

I got it auto-fixed after updating @nextcloud/eslint-config 👀

But same as #997 this requies adjustments to our code style first.

IMO, there should be no such details in the text documentation.

There is a linter/formatter for this. It defines all the rules, and they are actually rules — they are checked automatically.

I'd prefer to let developers decide when it is better.

The idea of code styles is to let no room for opinions 😉

When it is about places where both options are equal (e.g. using ;) or one in better in most of the cases (e.g. trailing commas).

But with this rule there are many cases where the opposite works well or better.

IMO, readability is more important than consistency.