[next] chore(master): merge master into next

[raimund-schluessler]

☑️ Resolves

• Merges master into next.

@ShGKme I didn't get #5178 to work properly with vue 3 yet. This needs some more work.

[ShGKme]

@ShGKme I didn't get #5178 to work properly with vue 3 yet. This needs some more work.

The issue is not related to this PR. Such usage of NcActions didn't work before as well, because findActions cannot find actions from sub-components (they need to be rendered first). So we have the same issue that we always had in Vue 2 (but more noticeable).

So this PR only adds an example of this limitation to the docs.

We need to find a more generic solution to solve #5171

[ShGKme]

Why change to startsWith?

[raimund-schluessler]

I thought we could introduce a naming convention for these wrappers. So if the components name starts with NcActions, we just pass it on. But that wasn't fully thought through and didn't work yet.

[ShGKme]

As an alternative, we could ask to add a custom option and check $options.

But this won't help in a general case. Developers may make wrappers for a list of actions

<template>
  <div>
    <NcActionButton />
    <NcActionInput />
  </div>
</template>

Or dynamic actions. Like, I dunno,

<template>
  <NcActionButton v-if="iLikeButtons" /> 
  <NcActionInput v-else-if="iDont" />
</template>

[susnux]

Or dynamic actions. Like, I dunno

Have this in forms: https://github.com/nextcloud/forms/blob/e1cfbc737234e0bd3ff10f8a1222223a8093e254/src/views/Results.vue#L134

[ShGKme]

Have this in forms:

This will work. I meant when those <template>...</template> are templates of new custom components.

<template>
  <NcActionButton v-if="iLikeButtons" /> 
  <NcActionInput v-else-if="iDont" />
</template>

<script>
export default {
  name: 'MyAction'
}
</script>  

and then

<template>
  <NcActions>
    <MyAction />
  </NcActions>
</template>

[raimund-schluessler]

Yes, this didn't work at all with next. But I thought we should at least get the same behavior as for master. But due to findActions, wrapped actions do not show up at all.

[ShGKme]

Yes, this didn't work at all with next. But I thought we should at least get the same behavior as for master. But due to findActions, wrapped actions do not show up at all.

I have found a small number of apps that require this feature. Text, Mail. I hope, we will find a solution until they migrate =D

[raimund-schluessler]

Ok, I would propose that we do a simple merge of master into next here without trying to fix the underlying problem and then proceed to find a solution in a new PR. After all, it doesn't work in next anyway, so we don't make it worse.

[raimund-schluessler]

Since next uses vitest to run the tests, we had to install @vitest/coverage-v8. I did this and also regenerated package-lock.json to get the latest dependencies.