Rails%203%20In%20Action

320 CHAPTER 12 Sending email
the email body checking line in your scenario and rerun your feature. You should see
the following:
Date: [date]
From: ticketee@gmail.com
To: alice@ticketee.com
Message-ID: [message_id]@[you].mail
Mime-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
This is a raw version of the email that alice@ticketee.com will receive when
bob@ticketee.com updates the ticket. As you can see from this raw version, there’s
nothing else to this email, and therefore there’s no content that will be displayed. To
make this final step pass, you must define some content for your email, which you
can do by defining a template.
12.1.5 An Action Mailer template
Templates for Action Mailer classes go in app/views because they serve an identical purpose
as the controller views: they display a final, dynamic result to the users. Once you
have this template in place, the plain-text email a user receives will look like figure 12.1.
As shown in the figure, you need to mention who updated the ticket, what they
updated it with, and provide a link to the ticket. Let’s put the template for your
comment_updated method at app/views/notifier/comment_updated.text.erb, as shown
in the following listing.
Listing 12.3 app/views/notifier/comment_updated.text.erb
Hello!
has just updated the
ticket for
. They wrote:
You can view this ticket on line by going to:
Wait, hold on! text.erb? Yes! This is the template for the plain-text version of this
email, after all. Remember, the format of a view in Rails is the first part of the file
extension, with the latter part being the actual file type. Because you’re sending a textonly
email, you use the text format here. A little further down the email road, you’ll
look at how you can send out HTML emails too.
Figure 12.1
Your first email