You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At a couple of places during parsing, we need to skip ahead to figure out what to feed Acorn — inside read_pattern, and as of #12070 inside snippets using a separate mechanism. The logic fails if characters like { appear inside strings, comments or regular expressions and are not balanced:
<!-- ok -->
{#eachxas { y ='z' }}{/each}
<!-- not ok -->
{#eachxas { y ='{' }}{/each}
Speaking of which it just occured to me: right now if the function parsing fail we just silently fail...we should probably throw (same for unbalanced parentheses) right?
Describe the bug
At a couple of places during parsing, we need to skip ahead to figure out what to feed Acorn — inside
read_pattern
, and as of #12070 inside snippets using a separate mechanism. The logic fails if characters like{
appear inside strings, comments or regular expressions and are not balanced:Reproduction
link
Logs
No response
System Info
Severity
annoyance
The text was updated successfully, but these errors were encountered: