Skip to content
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

Space in expression results in error #30

Closed
d3bgger opened this issue Feb 11, 2015 · 2 comments
Closed

Space in expression results in error #30

d3bgger opened this issue Feb 11, 2015 · 2 comments

Comments

@d3bgger
Copy link

@d3bgger d3bgger commented Feb 11, 2015

If there is a space inside an expression (e.g {{> partialName}} instead of {{>partialName}}) the binder crashes ("Reached unparseable token in expression").
Same happens when {{ property }} or {{# each mainmenu}} or {{# if isSelected}}

This is not happening in js library, so templates written for client side binding, might not work in server!

thanks

@rexm
Copy link
Collaborator

@rexm rexm commented Feb 15, 2015

Version 1.2.5 handles whitespace correctly for {{ path }} and {{ > partial }}. More work needs to be done to handle # and /... probably need to separate out those characters from the WordParser and create a new BlockParser to distinguish between WordExpressionTokens and block tokens.

@rexm
Copy link
Collaborator

@rexm rexm commented Apr 11, 2015

Updated NuGet 1.3.2

zjklee pushed a commit that referenced this issue Oct 12, 2020
Configure  `Release Drafter`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants