[next] fix(NcActionInput): listen to correct events

[raimund-schluessler]

☑️ Resolves

• This PR fixes NcActionInput to listen to the correct events of its child components. Before, the events of its childcomponents would not trigger an update of the model value.
• Fix [next] NcActionInput does not listen to correct events #5229

[ShGKme]

Makes sense.

I haven't tested, but it looks like input and change events doesn't work anymore with this PR. As they only proxied the same native events with native Event payload, we probably can just remove them from the emits declaration to bring them back. (Will work as a part of v-bind="$attrs")

[raimund-schluessler]

Makes sense.

I haven't tested, but it looks like input and change events doesn't work anymore with this PR. As they only proxied the same native events with native Event payload, we probably can just remove them from the emits declaration to bring them back. (Will work as a part of v-bind="$attrs")

@ShGKme I removed them from the emits declaration and @change and @input are emitted now. Unfortunately, they are emitted twice, do you have an idea why? Could this be a problem with NcTextField?

[ShGKme]

@ShGKme I removed them from the emits declaration and @change and @input are emitted now. Unfortunately, they are emitted twice, do you have an idea why? Could this be a problem with NcTextField?

Component is missing inheritAttrs: false.

Once event listener is set by v-bind="$attrs" on the input element itself, and once on the root element <li> by the default inheritance (input and change events bubble).

Probably, we should add vue/no-duplicate-attr-inheritance, I saw this issue in many places already...

[raimund-schluessler]

Setting inheritAttrs: false for NcActionInput might then break things we want, like style or css no?

[raimund-schluessler]

@ShGKme I added inheritAttrs and it fixes the double call to the handler. I guess if we notice, we need css and style we will have to add it manually later.

[ShGKme]

Setting inheritAttrs: false for NcActionInput might then break things we want, like style or css no?

Yes, but using v-bind="$attrs" without inheritAttrs: false is always an issue, it duplicates everything. We can add class to props as we did in other places to set it on the root.

[raimund-schluessler]

Setting inheritAttrs: false for NcActionInput might then break things we want, like style or css no?

Yes, but using v-bind="$attrs" without inheritAttrs: false is always an issue, it duplicates everything. We can add class to props as we did in other places to set it on the root.

Done.