The global and local scope of a variable

[GiggleLiu]

Current parser will search for local scope first and then the global scope, e.g.

julia> render("{{#l}}{{first}}{{second}}{{/l}}{{first}}", Dict("l"=>("x"=>"y"), "first"=>"z"))
"xyz"

Is it possible to invoke the global variable when names clash? e.g. with a !

julia> render("{{#l}}{{!first}}{{second}}{{/l}}{{first}}", Dict("l"=>("x"=>"y"), "first"=>"z"))
"zyz"

Note:
In my using case, I wish to identity the (global) variables that a user need to provide by inspecting the string only. Which means the global variables used in the local context should be identified. In Mustache.js, the global variables can not be accessed, see: janl/mustache.js#399 .

[jverzani]

Hmm, I think this would require modifying lookup in context.jl. In glancing at the code the default is fairly baked in, but let me think about it.

[jverzani]

Can you check if #129 does what you want? I used ~ in place of !, but with this PR the following works:

julia> render("{{#l}}{{~first}}{{second}}{{/l}}{{first}}", Dict("l"=>("x"=>"y"), "first"=>"z"))
"zyz"

julia> render("{{#l}}{{first}}{{second}}{{/l}}{{first}}", Dict("l"=>("x"=>"y"), "first"=>"z"))
"xyz"

I'm not sure I implemented it properly, so some testing would be nice.

[jverzani]

This example exposed an issue with using Pair elements in a view. They were passed off to the catch all and so first matches the fieldname first in the pair. It seems that pairs should parallel a dictionary, though, where the variable should match the key and return the paired value. I made that the default going forward, but special cased the use of first and second for now.

Without that change, this example wasn't working:

tpl = mt"""
{{#:one}}
{{#:two}}
{{~:x}}
{{/:two}}
{{/:one}}
"""
d = Dict(:two=>(:x=>3), :x=>2)
render(tpl, one=d) # "2\n"
render(tpl, one=d, x=1) # "1\n"
tpl = mt"""
{{#:one}}
{{#:two}}
{{:x}}
{{/:two}}
{{/:one}}
"""
render(tpl, one=d, x=1) # "3\n"

[GiggleLiu]

Nice, I am happy with the PR, it solves my issue. It would be good to put the above examples in the tests to help people understand.

Regarding your concern, I think

d = Dict(:two=>Dict(:x=>3), :x=>2)

is more intuitive.
But it does not harm to allow both.