We try to keep our books accurate, but sometimes mistakes creep in. This page lists the errors submitted by our astute readers. If you've found a new error, please submit it.

The latest version of the book is P1.0, released almost 3 years ago. If you've bought a PDF of the book and would like to upgrade it to this version (for free), visit your home page.

Key: Typo Tech. Error Suggestion Not a problem Next edition

By default this page displays the errata for the latest version of the book. If you have a previous version, select it here:  

(To find out what version you have, look at the copyright page, a few pages in from the front of the book. If it says (say) 'Second Printing', then here it'll be P2.0. If there are interim PDF releases in that printing, they'll be 2.1, 2.2, and so on.)

PDF Paper Description Found in Fixed in
vi
#47326: Copyeditor is listed as Kim Wimpsett. I thought Molly McBeath was the copyeditor for this one. (The number of people who care might be countab...more...
P1.0
30-Jul-11
5

#49308: The image of Figure 1 on the iPad only show the bars in blue and green. No labels or legend. They are blacked out.--Jonathan Lim

P1.0
12-May-12
17
#48713: There is a typo at the top of the page, in the Joe Asks box, so this: "the test/ directory, refixed with test_, to similarly named files in...more...
P1.0
13-Feb-12
19
#47786: In the initial creation of the user2.1_spec.rb, the line: require 'user' should be used just after the the spec_helper require line, in ...more...
P1.0
19-Oct-11
20
#49317: Of course, the User class doesn’t exist yet, so the failure of this test will drive us to create it: There is no test yet - we have only wr...more...
P1.0
12-May-12
26

#49318: But it’s essential that we not leave the test in this state.

s/this/that/--Jonathan Lim

P1.0
12-May-12
31

#47964: Refixed. -> prefixed--Brian maltzan

P1.0
19-Nov-11
45
#47790: Three lines from the bottom on page 45 there is the commnad line to create the gem: $ jeweler --rspec --gemcutter --create-repo autotest-st...more...
P1.0
20-Oct-11
47

#47791: On line 4 from the top the line:

...Firing up autospec ...

shouldn't that be:
...Firing up autotest ...--Kosmas Chatzimichalis

P1.0
20-Oct-11
81
#47940: You write the following: ":But first, we have to add it to our Gemfile: $ gem install watchr" Probably meant add it to the GemFile an...more...
P1.0
12-Nov-11
82
#47809: As the watcher script file can be named everything we want, wouldn't it be a better idea to have the watchr script file (rails.watchr), named ...more...
P1.0
24-Oct-11
88
#47810: Would it be a good idea to replace the Spork + Watchr automation with Spork + Guard automation, as Guard seems to be more recently updated? I...more...
P1.0
24-Oct-11
88
#47306: At the bottom of the page in the "Automating Spork with Watchr", you say "To start out, let's add some watch() for RSpec specs:" and you don't...more...
P1.0
22-Jul-11
91
#47132: "So if we restart Watchr and make a change to one of our specs (say, gro- cery_list_spec.rb), we get output that looks like this: Finished in...more...
Ben Rady says: The watch('^spec/(.*)_spec\.rb') { |m| run_test_matching(m[1]) } call in the rails.watchr file is intended to handle this case. Is there a problem with that call?
B4.0
30-May-11

Stuff To Be Considered in the Next Edition

PDF Paper Description Found in Fixed in
0

#46378: It will be better using "bundler" instead of "jeweler".

B2.0
10-Feb-11
16
#45918: I am a newbie to ruby which means I have to follow your book step by step. From page 16, I execute the below two commands with no problem:...more...
B2.0
07-Dec-10
89
#45204: "One great way to create a feedback loop for views in our web application is to turn over responsibility for refreshing the browser to our con...more...
B1.0
02-Oct-10