Some confusions about Vuejs3

[taozuhong]

What problem does this feature solve?

1. Example code add Composition api support
   Vuejs docs recommend Composition api, but most of example code are Options api, so please add Composition api code example stay with Options api code example together.
   I do believe it will be good for Composition api.

2. Improve the Composition api compatible with Options api
   Vuejs docs say the Composition api equal to Options api, But I found that the example code has much more different, like: mounted ==> onMounted, computed ==> onComputed / ...,

   Why not let them use the same name in Composition api and Options api?
   Why not import them(ref/mounted/computed/created) automatically?
   I do think using the same name will be accepted quickly by most of users.

[chenxch]

1.Documentation can be switched to Composition api, some documents may have options api + setup writing method, I think this part is actually quite interesting, this is more like an intermediate state from options api to setup script. As for using it together, I have experienced it in a project around me. Two students maintain the same code. Student A will use setup(), and student B will still use data/method. You will crash when checking the code, so it is recommended is to choose one of them.

2. I think the degree of acceptance is okay, and it is not at a very awkward level, and from the perspective of functional development, there is a verb that is very reasonable. As for the default import, some of them are not used. If you really want to import automatically, there are already plug-ins to achieve it.

unplugin-auto-import

Hope that can solve your confusion.