The case-sensitive matching works well when there is only one variable of one spelling. When there are multiple variables of same spelling but different upper/lower cases, things get messged up. For example:
var templateString = "Example {{TEST}} {{test}} | {{test2}} | {{TEST3}} {{test3}} | {{TesT}}";
var template = Handlebars.Compile(templateString);
var data = new ExpandoObject();
data.TryAdd("TEST", "Upper");
data.TryAdd("test", "Lower");
data.TryAdd("test2", "Lower2");
data.TryAdd("test3", "Lower3");
data.TryAdd("TesT", "Last");
var output = template(data);
Console.WriteLine(output);
prints
Example Upper Upper | Lower2 | | Upper.
If I use Handlebars.js, it prints
Example Upper Lower | Lower2 | Lower3 | Last.
It looks like the first match/unmatch, messed up all the subsequent same-spelling match.
The case-sensitive matching works well when there is only one variable of one spelling. When there are multiple variables of same spelling but different upper/lower cases, things get messged up. For example:
prints
Example Upper Upper | Lower2 | | Upper
.If I use Handlebars.js, it prints
Example Upper Lower | Lower2 | Lower3 | Last
.It looks like the first match/unmatch, messed up all the subsequent same-spelling match.