Skip to content

Commit

Permalink
Update reactivity-fundamentals.md (#2439)
Browse files Browse the repository at this point in the history
Evidently, the loss of reactivity only occurs when deconstructing properties of primitive types, whereas properties of non-primitive types remain unaffected by this phenomenon.
  • Loading branch information
yinjg1997 authored Jul 21, 2023
1 parent b4ddd44 commit 99bda99
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/guide/essentials/reactivity-fundamentals.md
Original file line number Diff line number Diff line change
Expand Up @@ -445,7 +445,7 @@ The `reactive()` API has a few limitations:
state = reactive({ count: 1 })
```

3. **Not destructure-friendly:** when we destructure a reactive object's property into local variables, or when we pass that property into a function, we will lose the reactivity connection:
3. **Not destructure-friendly:** when we destructure a reactive object's primitive type property into local variables, or when we pass that property into a function, we will lose the reactivity connection:

```js
const state = reactive({ count: 0 })
Expand Down

1 comment on commit 99bda99

@pmart25
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No es desestructurable: cuando desestructuremos una primitiva de de un objeto reactivo en variables locales, o cuando pasemos esa propiedad a una función, perderemos la conexión de reactividad:

Please sign in to comment.