From 5955ad191e5de7f95a6fb124d1d5a4fad46923e3 Mon Sep 17 00:00:00 2001 From: Brian Lim Date: Thu, 1 Jun 2017 18:04:07 -0400 Subject: [PATCH] Additional clarification with example --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 0d5ff11..e7a9c1a 100644 --- a/README.md +++ b/README.md @@ -497,9 +497,7 @@ Mustache.render(template, view, { The wording above with regard to partials "thought of as a single, expanded template", is exact. -That is, partial view data is not nested as expected with other view rendering engines. - -In other words, `Contexts` are currently not supported. +That is, partial view data is not nested nor is there a way to specify `Context`. For example, @@ -523,7 +521,11 @@ var partial = '{{#names}}Hello, my name is {{name}}.{{/names}}' console.log(Mustache.render(template, view, { partial: partial})); ``` -does not output the expected `test name 4` or `test name 5`. +does not output the expected `test name 4` or `test name 5`. The output is actually + +``` +Hi, test name 2!Hi, test name 3! PARTIAL TEST : Hello, my name is test name 2.Hello, my name is test name 3. +``` Therefore, the JSON object must be flat / flattened when using partials with no key conflicts.