fix: considering empty arrays as falsy values (#5)

jmjuanes · Apr 8, 2024 · 6d0e232 · 6d0e232
1 parent d3195c6
commit 6d0e232
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 2 deletions.
diff --git a/index.js b/index.js
@@ -30,8 +30,8 @@ const compile = (tokens, output, ctx, opt, index, section) => {
             const negate = tokens[i].startsWith("^");
             if (!negate && value && Array.isArray(value)) {
                 const j = i + 1;
-                value.forEach(item => {
-                    i = compile(tokens, output, item, opt, j, t);
+                (value.length > 0 ? value : [""]).forEach(item => {
+                    i = compile(tokens, value.length > 0 ? output : [], item, opt, j, t);
                 });
             }
             else {

diff --git a/test.js b/test.js
@@ -67,6 +67,13 @@ describe("{{# xyz }}", () => {
         assert.equal(m("{{#items}}{{name}}-{{/items}}", data), "Susan-Bob-");
     });
 
+    it("should not iterate over an empty array", () => {
+        const data = {
+            items: [],
+        };
+        assert.equal(m("List of items: {{#items}}{{.}},{{/items}}", data), "List of items: ");
+    });
+
     it("should throw an error for unmatched end of section", () => {
         const data = {name: "Bob"};
         try {