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

Filtering using deep equality


String equality works well when you need to compare two object references or two primitive values. But what about the cases where you want to compare something complex, such as two maps? Strict equality doesn't work here because they're two distinct references, even though their keys and values are the same. Immutable.js provides tools for performing deep collection comparisons.

Using the is() function and the equals() method

Immutable.js exports an is() function, which is used to compare two values. It can compare primitive JavaScript types using the same semantics as Object.is(), and it can do deep comparisons between two Immutable.js collections. When you pass two collections to is(), it will actually call the equals() method of the first collection. This means that you can be more direct if you know that you're comparing two collection types by calling equals(). If you don't know what you're comparing, is() is the better choice.

Let's start by comparing some...