From a2d0939a0f722061fb65d69c6fe73032971b562d Mon Sep 17 00:00:00 2001 From: Ivan Germanov Date: Fri, 18 Mar 2022 11:23:00 +0100 Subject: [PATCH] Fix broken 'ref-unwrapping-in-templates' link to 'deep-reactivity' --- src/api/composition-api-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/api/composition-api-setup.md b/src/api/composition-api-setup.md index 59c20c2be6..3f1e6a5f42 100644 --- a/src/api/composition-api-setup.md +++ b/src/api/composition-api-setup.md @@ -38,7 +38,7 @@ export default { ``` -Note that [refs](/api/reactivity-core.html#ref) returned from `setup` are [automatically shallow unwrapped](/guide/essentials/reactivity-fundamentals.html#ref-unwrapping-in-templates) when accessed in the template so you do not need to use `.value` when accessing them. They are also unwrapped in the same way when accessed on `this`. +Note that [refs](/api/reactivity-core.html#ref) returned from `setup` are [automatically shallow unwrapped](/guide/essentials/reactivity-fundamentals.html#deep-reactivity) when accessed in the template so you do not need to use `.value` when accessing them. They are also unwrapped in the same way when accessed on `this`. :::tip `setup()` itself does not have access to the component instance - `this` will have a value of `null` inside `setup()`. You can access Composition-API-exposed values from Options API, but not the other way around.