vuejs / composition-api-rfc Goto Github PK

The Documentation Is Limited For How To Use Types In Props. It Can Help Me To Use Interface As A Type For A Prop Instead Of Using Object By Default.

When I read compositon-api-rfc document in website, I found the code shown above. I don't know if this code is right. In my opinion, the code in the template should be

<template>
  <div :ref="root"></div>
</template>

and it is my first contact with vue3, and i don't kown the correct code.

https://vue-composition-api-rfc.netlify.com/#code-organization

Here are few images, all of them unclickable and even if I open it in a new tab - they are in low resolution.

Example

I think is a good idea for people is not good at english.
I have translated the docs into Chinese, and whould you like to accept it?

const myRef = toref(someVar)

const toref = isRef(someVar) ? someVar : ref(someVar)

why unref & toref not a pairs

解套
解开
解包

个人倾向于第三种， 我是学网络工程的，感觉 wrap 概念和TCP/IP 4层协议的工作模式类似，各个网络设备不断的对网络报文 包装 和 解包， ref reactive 也有点像是给普通对象加了一个包装。

When we click at the "API Reference" link at the upper right corner, pointing to https://vue-composition-api-rfc.netlify.com/api/ - it redirects to https://vue-composition-api-rfc.netlify.com/api.html - and as a side-effect, the link does not get the pretty green underline below it.

I am annoyed by this tiny detail... if this is a super-easy quick fix, then please consider fixing it. Otherwise, please just close this issue.

Thanks!

In api.md

• Having props as a separate argument makes it easier to type it individually (see TypeScript-only Props Typing below) without messing up the types of other properties on the context. It also makes it possible to keep a consistent signature across setup, render and plain functional components with TSX support.

'#typescript-only-props-typing' seems to have disappeared.

To get type inference for the arguments passed to setup(), the use of defineComponent is needed.
'#defineComponent' seems to have disappeared.

Thanks !

setup function will be called before the beforeCreate hook.

setup

Is there still any beforeCreate hook? Or this is a misspelling for beforeMount?