<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/ruby-gems/chef.git/spec/data/templates/failed.erb, branch https</title>
<subtitle>github.com: opscode/chef.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/ruby-gems/chef.git/'/>
<entry>
<title>Improving error handling for template render</title>
<updated>2019-05-26T12:47:06+00:00</updated>
<author>
<name>Gabriel Mazetto</name>
<email>brodock@gmail.com</email>
</author>
<published>2019-05-17T03:31:51+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/ruby-gems/chef.git/commit/?id=bf23769d7901a79623732d0db68d11a832b3ab40'/>
<id>bf23769d7901a79623732d0db68d11a832b3ab40</id>
<content type='text'>
While Chef already implements a nice amount of information
in `TemplateError#to_s`, when using ChefSpec with RSpec, the `#to_s`
is not called, leaving us with no source information for template
errors.

By adding the filename to `Erubis::Eruby` initialization, we can get
a better backtrace that will show up in RSpec output.

Signed-off-by: Gabriel Mazetto &lt;brodock@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
While Chef already implements a nice amount of information
in `TemplateError#to_s`, when using ChefSpec with RSpec, the `#to_s`
is not called, leaving us with no source information for template
errors.

By adding the filename to `Erubis::Eruby` initialization, we can get
a better backtrace that will show up in RSpec output.

Signed-off-by: Gabriel Mazetto &lt;brodock@gmail.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
