$slots not reactive outside template about core

[linzhe141]

However, it is reactive when used in a template?

The componentUpdateFn of the component will update the slots and execute the render function when it is re-executed, so the slots in the render function are the updated slots.

[skirtles-code]

There was a similar issue opened recently, #11227. The description of the problem is different, as is the use case, but I believe the underlying cause is the same: the slots object isn't reactive and is being used outside the rendering of its owner component.

I'm wondering whether the decision to make the slots object non-reactive should be re-evaluated. I think it made sense back in a Vue 2 Options API context, but maybe it isn't such a good fit for where Vue is now?

It feels similar to $refs and $attrs. Previously they were just plain objects, but that didn't work well with the Composition API, so they've both been 'replaced' by alternatives that support reactivity, or at least partial reactivity.

I assume the reason it isn't reactive is because of the extra overhead, but is that really significant enough to worry about if it makes slots more difficult to use in more advanced use cases?

I also wonder whether making slots reactive might benefit Vapor mode.

---

Bit of a tangent, but more generally I wonder whether the current approach of forcing a child to re-render when the props or slots change is actually the best way to go. While I can understand why it was done that way, it is a problem I've hit a few times and it can be really difficult to work around.

Perhaps, rather than always forcing a re-render, it could check whether the relevant job has been added to the scheduler queue and only do the re-render if it has? That approach might already be viable for props, though for slots it would need reactivity adding to the slots object.

[linzhe141]

Because instance's slots is not a reactive object, but a normal object

[geiregjo]

However, it is reactive when used in a template?

[LinusBorg]

However, it is reactive when used in a template?

It's not, actually. When the parent changes the number of slots it passes down, it tells that child component "hey, you need to re-render". And during that re-render, triggered by the parent component, not by the slots object, you read the sot object's properties again. That's why they are updated in the template.

[geiregjo]

Ok, I'll use onBeforeUpdate to detect slot changes then.

Just wondering, is this worth a feature request?

[yyx990803]

closing as a duplicate of #11227 as the root cause is the same.