-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Templates disallow unescaped braces even after changing interpolation delimiters #14019
Comments
Upon further investigation, I realize that escaping
The original reason for allowing making interpolation strings configurable was to be able to type |
We should update the error message to display the active delimiters instead of having |
Duplicate of #11859 |
Other strange case with braces. I want to escape double braces for show an example,
Currently, my solution, add a zero-width joiner (
|
I've long given up trying to fit a |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I'm submitting a ... (check one with "x")
Current behavior
When interpolation delimiters are changed to
[[
and]]
, having an unescaped{
in template still throws an error (including{{
).Expected behavior
{
should be allowed in templates if interpolation delimiters are changed.Minimal reproduction of the problem with instructions
http://plnkr.co/edit/5Kl9w2Mpct9z7ljEgogS?p=preview
What is the motivation / use case for changing the behavior?
One would normally change interpolation string because one needs
{{
for something else (eg. LaTeX syntax uses{
heavily).Please tell us about your environment:
Browser: all
Language: TypeScript
The text was updated successfully, but these errors were encountered: