Kristian Dalgård

I think writing each variant separately, like you are doing, is the best solution, as long as they are that small and differ both in their content and class name....

+1 There is a `try {` block wrapping the compiler call, and a `catch` which tries to make the output exception prettier, but I think the concept works a bit...

@mordra: For `dalgard:viewmodel`, I recommend the syntax that has since been added by [`dalgard:jade`](https://github.com/dalgard/meteor-jade).

You can simply write: ``` jade each contexts option(value=this selected=isContextSelected) #{this} (Selected) ``` If all is well, the issue can be closed.

If `isContextSelected` is `true`, it _should_ result in a boolean `selected` attribute.

Does it work with Blaze syntax (embedded in Jade)?

I've modified a fork of this package with a new way of writing dynamic attributes, along with a few other useful features. The fork has been released as [`dalgard:jade`](https://github.com/dalgard/meteor-jade). Would...

Yes, I've modified a fork of this package to support passing arguments to helpers, together with a few other useful features. The fork has been released as [`dalgard:jade`](https://github.com/dalgard/meteor-jade). I will...

I've modified a fork of this package to support passing arguments to helpers, along with a few other useful features. The fork has been released as [`dalgard:jade`](https://github.com/dalgard/meteor-jade). Could you please...

I've modified a fork of this package that makes it possible to pass arguments to attribute helpers, besides some other useful features. The fork has been released as [`dalgard:jade`](https://github.com/dalgard/meteor-jade). I...