-
Notifications
You must be signed in to change notification settings - Fork 341
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
Allow for looping array of string #72
Conversation
content: `{selection:['yellow','green','blue']}' template: `{#selection}{value}{/selection}`
Hi, I like the idea. As many times, I prefer to use the mustache way, eg |
Hey, nice. I did not know the mustache way… Testing fails for me though. On 30 Aug 2014, at 22:44, edi9999 notifications@github.com wrote:
|
Yes it's not yet implemented in the library, it was just as an idea. But it's probably a one liner. |
It should be in the DocUtils.defaultparser |
My fix is not working though, I was just testing... I'll look into defaultparser |
Updated as of v0.7.3, on npm too |
Awesome! |
I was testing this, but the solution does not work with angular parser enabled. Any way to do this? |
I now use this code to have to detect expressions = require 'angular-expressions'
angularParser = (tag) ->
return {get: (s) -> s} if tag == '.'
get: expressions.compile tag |
Yes that should do the trick. |
content:
{selection:['yellow','green','blue']}
template:
{#selection}{value} {/selection}
result:
yellow green blue