Prevent to generate invalid ruby code on embedded heredoc

[pocke]

Problem

Slim generates invalid ruby code if ruby: block has a heredoc at end.

For example:

$ cat test.slimo
ruby:
  v = <<-MSG
  foobar
  MSG
= v

$ slimrb test.slim
SyntaxError: test.slim:8: can't find string "MSG" anywhere before EOF
test.slim:2: syntax error, unexpected end-of-input, expecting tSTRING_CONTENT or tSTRING_DBEG or tSTRING_DVAR or tSTRING_END
; v = <<-MSG
            ^
  Use --trace for backtrace.

This cause is a semicolon after delimiter of heredoc(MSG).

$ slimrb -c test.slim
_buf = '';
; v = <<-MSG
foobar
MSG;
; _buf << ((::Temple::Utils.escape_html((v))).to_s);
; _buf

Heredoc delimiter does not allow putting a semicolon after the delimiter.
So, slim generates invalid ruby code from the example.

Solution

Add a newline to embedded ruby code.

For example:

$ slimrb test.slim
foobar

$ slimrb -c test.slim
_buf = '';
; v = <<-MSG
foobar
MSG
;
; _buf << ((::Temple::Utils.escape_html((v))).to_s);
; _buf

[k0kubun]

This line is testing that backtrace is properly created, i.e. unknown_ruby_method is called on lineno 6 in source. Consider the case your code after 10 :ruby filters raised error. The error backtrace would say it raised an error on 10 lines after the actual location. It will make it hard to debug Slim template.

So this test should pass without modification. You need to generate another code to fix this problem.

[stonean]

Thank you for the contribution!