From 087f649609295c048857793ceb45ed117b93294c Mon Sep 17 00:00:00 2001 From: Mark Tinsley Date: Mon, 21 Sep 2015 21:11:57 -0500 Subject: [PATCH] "convert" vs "converting" I believe that's correct. --- source/guide/best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/guide/best-practices.md b/source/guide/best-practices.md index 91859a7b57..5f8224d4ea 100644 --- a/source/guide/best-practices.md +++ b/source/guide/best-practices.md @@ -29,7 +29,7 @@ new Vue({ }) ``` -The reason for this is that Vue observes data changes by recursively walking the data object and convert existing properties into reactive getters and setters using `Object.defineProperty`. If a property is not present when the instance is created, Vue will not be able to track it. +The reason for this is that Vue observes data changes by recursively walking the data object and converting existing properties into reactive getters and setters using `Object.defineProperty`. If a property is not present when the instance is created, Vue will not be able to track it. You don't have to set every single nested property in your data though. It is ok to initialize a field as an empty object, and set it to a new object with nested structures later, because Vue will be able to walk the nested properties of this new object and observe them.