Mastering Immutable.js

Is this really necessary?

There are some questions that you should ask yourself before going down the insertion index path:

• Do I want to maintain my own insertion index functionality?
• What about the case where list values change?
• Is there anything actually wrong with sorting the collection after persistent changes?
• Do I just sort on the fly as part of the sequence and side-effect workflow?

Maintaining the sort order of collections by finding the insertion index for new or changed values is harder than sorting the collection. You can sort the collection every time you push new values or change existing values:

const usingSort = myList  .push(2)  .push(4)  .sort();console.log('usingSort', usingSort.toJS());// -> usingSort [ 1, 2, 3, 4, 5 ]