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
@select breaks dot paths #42
Comments
@lastobelus there is a ticket for this. needs some thinking to fix it. |
closed since it is duplicate of #9 |
sethkinast
pushed a commit
to sethkinast/dustjs-helpers
that referenced
this issue
Dec 11, 2014
- Must be contained in a {@select} block - Renders its body if any truth test inside the {@select} block evaluates to true - Can be included multiple times inside a {@select} block. As part of this change, {@select} no longer clobbers the current context, so keys that begin with a dot work inside a {@select}. This closes LinkedInAttic#9, closes LinkedInAttic#42, closes LinkedInAttic#50, and closes LinkedInAttic#79.
Merged
sethkinast
pushed a commit
to sethkinast/dustjs-helpers
that referenced
this issue
Dec 13, 2014
- Must be contained in a {@select} block - Renders its body if any truth test inside the {@select} block evaluates to true - Can be included multiple times inside a {@select} block. As part of this change, {@select} no longer clobbers the current context, so keys that begin with a dot work inside a {@select}. This closes LinkedInAttic#9, closes LinkedInAttic#42, closes LinkedInAttic#50, and closes LinkedInAttic#79.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using @select, dot paths no longer work inside @eq branches.
This jsfiddle concisely demonstrates: http://jsfiddle.net/KdZMc/
The text was updated successfully, but these errors were encountered: