v1.0.11 - Error when using a partial with a name that contains a period.

[doowb]

In v1.0.10 we were able to call a partial with a name like this...

{{> myPartial.md }}

In v1.0.11 I get the following error:

Warning: Parse error on line 9:
{{> myPartial.md }}
-------------^
Expecting 'CLOSE', 'ID', got 'SEP'

[cappslock]

+1

[panthershark]

Related older ticket. If remember correctly, the period was a workaround for the slash breaking the parser.. or something like that.

#268

[victorwpbastos]

+1

[coen-hyde]

Yes I'm experiencing the same problem.

[carlos8f]

+1, as a patch release it crept in and broke my stuff.. ouch.

[wycats]

We have three options:

• Fix the parser to be super-greedy
• Support strings ({{> "foo/bar" }})
• Support literal ID syntax ({{> [foo/bar]}}) -- does this already work?

[leshill]

Hi @wycats,

Did you see the patch from @jamesgorrie for #526 which adds . to the list of allowed characters?

[victorwpbastos]

+1 for the pr #526

[kpdecker]

Neither "" nor [] work at this time from my reading of the parser definition. While we will add support for ., doing just that feels like a stopgap rather than a complete fix. Need to better define what the characters we want to allow inline and pick one of the escaping mechanisms above so users can work around it if they want to define something else.