fix(runtime-core): when props is typeof ref, they lose data and don't stay responsive

[yingpengsha]

Add the test cases for which props will be specially handled

[skirtles-code]

I'm curious what the goal is here. Why is it important that the props aren't wrapped in proxies?

I believe this will come into conflict with #8222, which wraps them in a proxy. If there's a compelling reason why those objects must not be readonly proxies then it may be necessary to tweak that PR.

[yingpengsha]

After such a long time, my memory has deviated.

I can only be certain of one thing: there was an unexpected event where reactive props caused the component to lose its reactive state.

However, upon re-examination, I've identified another issue. When declaring a view in this manner: h(Component, Ref), something gets lost.

This issue can be traced back to the guardReactiveProps function. I've revised the changes in the PR to include compatibility logic.

However, it seems that this does not quite match the results I initially observed. Whatever the case, this experience teaches us that whenever we submit a PR or ISSUE, we should thoroughly document the background and process to prevent forgetting details over time.

:)

/cc @skirtles-code

[skirtles-code]

It seems that the new changes you've pushed are unrelated to the original contents of the PR. It would probably have been better to open a new PR for these rather than reusing this one. The previous conversations and labels on this PR no longer make sense in the context of the new changes.

I'm not sure whether using h(Component, Ref) would be considered a valid use case. Could you provide more details of the actual use case? A playground example at https://play.vuejs.org/ might help us to understand why this is needed.

I also think you'd need to add a test case if you want to introduce this change.

[yingpengsha]

I will recall and reconsider the necessity of this change. If new information arises, I will submit a new PR to elaborate on it.