Learning JavaScript Design Patterns

Errata for Learning JavaScript Design Patterns

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.


Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 1
1

There have been a number of minor corrections made to the open-source version of the book. The changelog for these changes can be found here https://github.com/addyosmani/essential-js-design-patterns/commits/1.5.2, but we only need to pay attention to those made since October 27th. We need to apply the change made in each of the commits to the production version of the book. In most cases a simple search will locate the sentence, word, phrase or piece of code that was updated. e.g In https://github.com/addyosmani/essential-js-design-patterns/commit/3b3891410f6e1fe038f3357bbc2eb0a27bfe70e9 we can see that there was an indentation fix and a fix to the name of a variable.

Addy Osmani
O'Reilly Author 
Dec 11, 2012  Mar 01, 2013
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 1
Numerous

There have been a number of fixes made to the book since the last O'Reilly refresh. These changes can be found here in the changelog: https://github.com/addyosmani/essential-js-design-patterns/commits/1.5.2. Clicking any change will show the old text as well as the replacement text. For example: Correction to IIFE code samples: https://github.com/addyosmani/essential-js-design-patterns/commit/b92a7a086f25237c746790fbd76532dd91b8dde0 Missing arguments in one of the code samples: https://github.com/addyosmani/essential-js-design-patterns/commit/f5039856a7f9d2b4bf6c5a34f61fa3df4b17ccc5 Correction for observer code sample: https://github.com/addyosmani/essential-js-design-patterns/commit/69c722bfab98a4cb7f19d78ab71c87d3bb654971 Could a member of staff kindly check the last time the book was refreshed and work towards integrating these changes into the docbook so that we can get an update our to readers?

Addy Osmani
O'Reilly Author 
Apr 06, 2013 
PDF, ePub
Page 47
Figure 9-4

Starting with Figure 9-4, the figures in Chapter 9 do not match with the section for which they are intended; so for instance, 9-4 shows the Mediator Pattern, but it is in the section for Publish/Subscribe Pattern. This continues for the remainder of the chapter.

Note from the Author or Editor:
This is very strange and doesn't match up with QC2, which did contain the diagrams in the correct positions (we did some further text tweaks to that, but not to diagrams). Page 47: 9-4. Confirmed that the Mediator pattern diagram is presented at the top of the page where the Publish/Subscribe diagram should be shown. Figure 9-5 should be the Mediator pattern diagram but is instead shown as the Prototype pattern diagram. Page 69: The Prototype Pattern diagram shows the Command pattern diagram. Figure 9-7: shows the facade pattern diagram where the command pattern diagram should be shown. Page 74: Figure 9-8 shows the Factory pattern where the Facade pattern should be shown. In short: it would appear that the final PDF that was distributed had the technical diagrams mixed up from page 47 onwards. The images themselves are correct, just positioned in the wrong places. We need to fix this by double checking the list of diagrams produced by the graphics department against each section expecting a diagram (basically the main section covering patterns).

Piers Hollott  Aug 28, 2012  Sep 14, 2012
Mobi
Page 2015
The Revealing Module Pattern Code Sample

The publicSetName function in the Revealing Module Pattern code example is assigning its argument strName to a global variable, privateName. I think it should be assigning strName to privateVar. function publicSetName( strName ) { privateVar = strName; }

Note from the Author or Editor:
This error was addressed in the latest commits to the open-source version of the book. Please see Oct 27th onwards for the changes required to bring the latest inline with this: https://github.com/addyosmani/essential-js-design-patterns/commits/1.5.2

Jared Cacurak  Sep 17, 2012  Mar 01, 2013