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

@select breaks dot paths #42

Closed
lastobelus opened this issue Mar 27, 2013 · 2 comments · Fixed by #107
Closed

@select breaks dot paths #42

lastobelus opened this issue Mar 27, 2013 · 2 comments · Fixed by #107

Comments

@lastobelus
Copy link

When using @select, dot paths no longer work inside @eq branches.

This jsfiddle concisely demonstrates: http://jsfiddle.net/KdZMc/

@vybs
Copy link
Contributor

vybs commented Mar 27, 2013

@lastobelus there is a ticket for this. needs some thinking to fix it.

#9

@vybs
Copy link
Contributor

vybs commented Apr 14, 2013

closed since it is duplicate of #9

@vybs vybs closed this as completed Apr 14, 2013
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.
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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants