Class shorthand does not work when expressions are in coffeescript

[antoinegoutagny]

The class shorthand does not work when expressions are in coffee. The following tag:

<my-tag>
    <div class={ className: true }>Hello</div>
</my-tag>

When run through the compiler with the -t coffee --expr options, is translated to the following:

riot.tag('my-tag', '<div class="{({ className: true })}">Hello</div>', function(opts){})

Hence in the update(expressions, tag) method, expr is an object and the attribute is removed from the DOM instead of being updated.

One workaround is to compile tags without the --expr option and write expressions in pure JS instead of coffee. That isn't too cumbersome since expressions are supposed to be simple, but there's the overhead of switching between coffee and js depending on the part of the tag we're in.

[aMarCruz]

This is not a bug, it is a design conflict ;)
Anyway, there will be an option to disable preprocessing at expression level.

[antoinegoutagny]

Well, there's already an option to disable preprocessing at expression level, it's the --expr flag (or its absence).

[aMarCruz]

yeah, I mean disable the option only in certain expressions (i.e. shorthands)
something like {^ myclass: true }

[aMarCruz]

I'm closing this issue, new compiler will support exclusion of preproc with the caret, just like in the above example.