:javascript filter breaks #{local} variables

[alexgorbatchev]

on haml 2.0.9

```
require ‘haml/engine’

template_broken = ’
:javascript
– [1, 2, 3, 4].each do |item|
= “Hey #{item}”
’

puts Haml::Engine.new(template_broken).to_html
```

causes

```
(haml):3:in `to_html’: undefined local variable or method `item’ for # (NameError)
from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.0.9/lib/haml/engine.rb:149:in `to_html’
from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.0.9/lib/haml/engine.rb:149:in `instance_eval’
from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.0.9/lib/haml/engine.rb:149:in `to_html’
from haml.rb:9
```

however, this works just fine. notice that I replaced :javascript filter with regular %script tag.

```
require ‘haml/engine’

template_broken = ’
%script
– [1, 2, 3, 4].each do |item|
= “Hey #{item}”
’

puts Haml::Engine.new(template_broken).to_html
```

[nex3]

You’re misunderstanding the Javascript filter. Like other Haml filters, it doesn’t take Haml code; it takes Javascript code. For example:

```
:javascript
function foo() {
return “bar”;
}
```

[alexgorbatchev]

Have I missed this somewhere in the doc? It seems odd that I can’t generate output inline for a filter. Is this a technical limitation or by design? Think I saw something about scope issues in HAML code comments…

[nex3]

This is by design. You can put Ruby code in a filter using `#{}`, like so:

```
:javascript
var rails_version = #{Rails::VERSION::STRING.to_json}
```

but you can’t use Haml constructs like “-” and “=”. The purpose of filters is to allow non-Haml languages, like Javascript, to be embedded within Haml.