The latest version of the book is B4.0, released 2 months ago. If you've bought a PDF of the book and would like to update it to this version (for free), visit your home page.
By default this page displays the errata for the latest version of the book. If you have a previous version, select it here:
If you've found a new error, please submit it.
- Reported in: B4.0 (09-Apr-20)
Paper page: 9
It doesn't actually say it anywhere there, but in order to get yarn running, you'd need to install node.js and npm install yarn.
Otherwise you get a hard-to-read error while doing the first bundle exec rails webpacker:install
Maybe this should be told to the readers?--Ville Sipola
- Reported in: B4.0 (11-Apr-20)
PDF page: 14
Paper page: xii
The setup process probably requires some work.
Running ruby bin/setup for introduction / 01 stops with multiple problems.
There are simple things like the setup script running rails with a command starting with bin/rails while rails is in the same directory as the setup script.
But there are also more complex things like a whole lot of settings in database.yml and the postgresql database itself that would need to be set up before the setup can go through. None of those settings have been explained in the text. Maybe they should?--Ville Sipola
- Reported in: B4.0 (16-Apr-20)
PDF page: 44
In the package.json section you reference a library called “actionstorage”. I believe you meant *active*storage. --Julian Pinzon Eslava
- Reported in: B4.0 (23-May-20)
PDF page: 72
On page 72, near the bottom, we are told to include <%= stylesheet_pack_tag("application") %> in layouts/application.html.erb. It stands to reason that we should also remove the existing line that directly imports the framework, but this is not stated explicitly in the book. I checked the different versions of the app in the css folder of the book code, and though the direct import line has been removed in the application layout file, the stylesheet_pack_tag is not present in any version of this file. Furthermore, including it or not doesn't seem to make a difference.--Randy
- Reported in: B4.0 (17-Apr-20)
PDF page: 162
It should be @status not status. I couldn't update the seats without changing that--André Furquim Xotta
- Reported in: B3.0 (22-Mar-20)
PDF page: 197
Paper page: 189
The code snippets moving forward are probably from the wrong chapter, that is, /server rather than /state.
The text says things like "It’s just calling three other components: the VenueHeader and VenueBody we already had, and our new one, Subtotal." but the code is an older version without the Subtotal part--Claudio