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

each compile error #543

Closed
ariesjia opened this issue Mar 27, 2015 · 2 comments
Closed

each compile error #543

ariesjia opened this issue Mar 27, 2015 · 2 comments

Comments

@ariesjia
Copy link

i use coffee to write tag file .

each="{ items of  array}"

is ok ,

each="{ keys, items of  array}"

it will compile error : Warning: unexpected , Used --force, continuing.

@timzaak
Copy link

timzaak commented May 23, 2015

I also use coffee,
each ="{key,items in obj}" is wrong.
after reading the source code, I think it may be a good idea to compile the code in '{ }' by 'plainjs', because the code writen in '{}' is always treated as DSL of the riotjs, like 'angular filter'

@aMarCruz
Copy link
Contributor

This is related to #1090
the new compiler has generic support to avoid this issues. If the first character inside an expression is ^, the expression is not passed to any parser. This is some sort of type=none at expression level.
e.g.

each="{^ keys, items of  array}"

Maybe in a future version we can do that for ifand each automatically.

Edit: I'll close this issue now, feel free to open it if you consider it necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants