9
公开标注数
7
参与人数
2026-07-15 09:58:53
首次 Whisper
讨论活跃度
vuejs.org 近 17 周的公开 Whisper
少多
最新公开 Whisper
划选高亮2026-07-16 16:22:56
原文高亮摘录
“The .value property gives Vue the opportunity to detect when a ref has been accessed or mutated.”
Whisper 随想笔记
So basically .value is like a little spy Vue plants on your data.
划选高亮2026-07-16 13:19:56
原文高亮摘录
“ref() takes the argument and returns it wrapped within a ref object with a .value property”
Whisper 随想笔记
Hmm, why not just return the value directly? Seems like extra steps.
划选高亮2026-07-16 13:10:56
原文高亮摘录
“ref() takes the argument and returns it wrapped within a ref object with a .value property”
Whisper 随想笔记
So basically every reactive value is just an object with a .value inside, got it.
划选高亮2026-07-16 10:16:56
原文高亮摘录
“Vue uses a $ prefix when exposing its own built-in APIs via the component instance. It also reserves the prefix _ for internal properties.”
Whisper 随想笔记
Does that mean I can't use _count for my counter? Ugh.
划选高亮2026-07-16 10:07:56
原文高亮摘录
“Vue uses a $ prefix when exposing its own built-in APIs via the component instance. It also reserves the prefix _ for internal properties.”
Whisper 随想笔记
Good to know, I always wondered what the $ was for.
划选高亮2026-07-16 09:58:56
原文高亮摘录
“Vue uses a $ prefix when exposing its own built-in APIs via the component instance. It also reserves the prefix _ for internal properties.”
Whisper 随想笔记
Ah, so that's why my $_data broke everything
划选高亮2026-07-15 10:16:53
原文高亮摘录
“the Options API is implemented on top of the Composition API!”
Whisper 随想笔记
Makes sense, but I still prefer Options for simple components. Less boilerplate.
划选高亮2026-07-15 10:07:53
原文高亮摘录
“the Options API is implemented on top of the Composition API!”
Whisper 随想笔记
Wait, so the old way is just a wrapper? That actually explains a lot of weirdness.
划选高亮2026-07-15 09:58:53
原文高亮摘录
“the Options API is implemented on top of the Composition API!”
Whisper 随想笔记
So that's why they feel so consistent even when I switch between them.