From b6e2f76a454a9d9333f4a0d0469e7b20aa9b53f3 Mon Sep 17 00:00:00 2001 From: Robin Houston Date: Mon, 13 Mar 2017 22:03:14 +0000 Subject: [PATCH] Document whitespace compatibility difference with mustache --- README.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/README.markdown b/README.markdown index 4c333eb9..bfcf8be2 100644 --- a/README.markdown +++ b/README.markdown @@ -68,6 +68,7 @@ Block expressions have the same syntax as mustache sections but should not be co There are a few Mustache behaviors that Handlebars does not implement. - Handlebars deviates from Mustache slightly in that it does not perform recursive lookup by default. The compile time `compat` flag must be set to enable this functionality. Users should note that there is a performance cost for enabling this flag. The exact cost varies by template, but it's recommended that performance sensitive operations should avoid this mode and instead opt for explicit path references. - The optional Mustache-style lambdas are not supported. Instead Handlebars provides its own lambda resolution that follows the behaviors of helpers. +- Handlebars does not allow space between the opening `{{` and a command character such as `#`, `/` or `>`. The command character must immediately follow the braces, so for example `{{> partial }}` is allowed but `{{ > partial }}` is not. - Alternative delimiters are not supported.