Allow escaping of {{

[lazd]

\{\{ should not be processed by the parser implemented in #2

[cif]

Escapes are rendering the escape character in addition to the brace.

\{\{data.attributes.name\}\}   // renders same string instead of {{data.attributes.name}}

Is there a quick solution to this or should I dive in? I'm currently using the nodejs precompile() method

[lazd]

Looks like the grammar will have to be modified to allow this, currently the CONTENT token is matching escaped curly braces and just passing them along. I suppose we need another token that handles escaped braces and returns them as content without the backslash.

[cif]

Makes sense. Dustjs uses {~rb} and {~lb}.

Where is that implemented, part of handlebars/mustache?

[lazd]

The Mustache-like grammar is implemented here: https://github.com/lazd/DOMly/blob/master/lib/grammar-text.jison

[lazd]

@cif, I added escaped mustaches to the grammar, I think we should be good now.

My BISON skills are rusty, so I hope I've done it correctly :)

[cif]

Tried quite a few things within that file, unfortunately I'm in the same boat with the BISON. The escape characters are still being rendered with the updated grammar rules

One thought I had was to enable the use of } and { (entities in general), however during the precompile function those are converted into their respective {} at some point

[lazd]

Hmmm, I added a test and it's working nicely... Can you create a gist with the template you're trying to compile?

I've filed a question issue #20 to track the entities behavior you noticed. I don't think it's a problem, though.

[cif]

Pared it down to be simple as possible.

https://gist.github.com/cif/564137bfba495aad1d4e

Is there anything else I would have to update other than the rules here? https://github.com/lazd/DOMly/blob/master/lib/grammar-text.jison I installed via NPM last last week.

[lazd]

@cif, I see the error you're mentioning. DOMly isn't processing that string as it doesn't use any variables, I can put together a fix shortly.

[lazd]

@cif, the latest change should fix it!