From bc48b4606ab436a17f663249482c41704d8b57c0 Mon Sep 17 00:00:00 2001 From: Alexandre Bourget Date: Fri, 1 Jan 2016 16:08:39 -0500 Subject: [PATCH] Added documentation about variable scoping in "partials". --- docs/content/templates/partials.md | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/docs/content/templates/partials.md b/docs/content/templates/partials.md index 4f87e5e69..a05c9b32c 100644 --- a/docs/content/templates/partials.md +++ b/docs/content/templates/partials.md @@ -106,5 +106,21 @@ To reference a partial template stored in a subfolder, e.g. `/layout/partials/po Note that the subdirectories you create under /layout/partials can be named whatever you like. -**For more examples of referencing these templates, see [single content -templates](/templates/content/), [list templates](/templates/list/) and [homepage templates](/templates/homepage/).** +For more examples of referencing these templates, see +[single content templates](/templates/content/), +[list templates](/templates/list/) and +[homepage templates](/templates/homepage/). + + +Variable scoping +---------------- + +As you might have noticed, `partial` calls receive two paramters. + +1. The first is the name of the partial and determines the file +location to be read. +2. The second is the variables to be passed down to the partial. + +This means the partial _only_ be able to access those variables. It is +isolated and has no access to the outer scope. From within the +partial, `$.Var` is equivalent to `.Var`