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

Ordered maps


Maps don't preserve order the way that lists do. When you push a value to a list, the value will always be in the same position because lists are indexed. With maps, the order of a particular value doesn't matter because you can look it up by its key. When you're iterating over maps, ordering can become a problem though.

Order guarantees

The ordering of list values is guaranteed because lists are an indexed collection. Maps are a keyed collection, which means that the order in which key-value pairs are added isn't guaranteed to be preserved. For example, let's say that I call myMap.set('one', 1).set('two', 2). If you were to iterate over this map, one would probably come before two. But this is misleading, because there are no ordering guarantees when it comes to iterating over maps. This could be a problem if your application expects iteration ordering to be consistent.

Insertion order is not sort order

The answer to the iteration order problem with maps is to use an ordered map...