[Runtime] Component Props about core-vapor HOT 6 CLOSED

The essence of designing Vapor is: that we need to maximize compatibility with the existing behavior of Vue core.

• Currently, we don't need to consider macros like defineProps; they belong to the scope of SFC compiler and will ultimately be compiled into the props option.
• We need to support options like props, emits, and others, as well as the setup function. However, there's no need to implement the Options API such as data, created, computed, etc.
• Props should be stored in the ComponentInternalInstance for composable retrieval.
• As you mentioned the https://github.com/sxzz/vue-simple-props project. Currently, we might need a formal RFC or experiment first in Vue Macros before landing it in Vue Vapor.

from core-vapor.

I'm trying..

https://github.com/Ubugeeei/vuejs-core/tree/feat/component-props

from core-vapor.

I've probably implemented the basic functionality, so once I refine it a bit more, it seems like I'll be able to submit a PR.

Unlike the render function of traditional components, which generates new rawProps and patches them each time, we need to find a way to always get the latest values of the original props.
I tried implementing this by modifying the traditional initProps function and defining a getter using Object.defineProperty, but I wonder if there's a smarter way to do this. 😵‍💫

I'll raise a PR soon for a bit of discussion...

from core-vapor.

@sxzz
I've written a few drafts, but regarding the design of Props, has there been any discussion within the team, or is there a planned time to discuss this?

from core-vapor.

It's too long, and I haven't had enough time and read it yet...

from core-vapor.

Oh, I'm sorry for rushing you, I understand.
I'll wait until there's some progress! 💪🏻

from core-vapor.