Book Image

Mastering Immutable.js

By : Adam Boduch
Book Image

Mastering Immutable.js

By: Adam Boduch

Overview of this book

Immutable.js is a JavaScript library that will improve the robustness and dependability of your larger JavaScript projects. All aspects of the Immutable.js framework are covered in this book, and common JavaScript situations are examined in a hands-on way so that you gain practical experience using Immutable.js that you can apply across your own JavaScript projects. The key to building robust JavaScript applications using immutability is to control how data flows through your application, and how the side-effects of these flows are managed. Many problems that are difficult to pinpoint in large codebases stem from data that’s been mutated where it shouldn’t have been. With immutable data, you rule out an entire class of bugs. Mastering Immutable.js takes a practical, hands-on approach throughout, and shows you the ins and outs of the Immutable.js framework so that you can confidently build successful and dependable JavaScript projects.
Table of Contents (23 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Collection equality


There are two types of equality checks that you can use with Immutable.js collections: strict equality and deep equality. Strict equality is cheaper and therefore it is faster than deep equality. On the other hand, there are some things that deep equality can do that strict equality cannot.

Strict equality and mutative methods

In JavaScript, the strict equality operator compares the memory address of values, not the actual values. Immutable.js collections can't be changed, which means that the strict equality operator doesn't make much sense to use with Immutable.js collections. There's one important use case where this operator does make sense to use with Immutable.js collections—change detection.

Detecting changes

What's special about mutative methods, or methods that perform persistent changes, is that they return the same collection instance if nothing actually changes. This is a big deal because it means that you can use strict equality to detect a change in the collection...