ECMAScript Collection Insecurities and Prevention

ECMAScript Insecurities and Prevention – Part 4

ECMAScript 6

Foreword: In this part of the series, I explain the insecurities with collections and how to prevent them.

By: Chrysanthus Date Published: 16 Jul 2016

Introduction

This is part 4 of my series, ECMAScript Insecurities and Prevention. In this part of the series, I explain the insecurities with collections and how to prevent them. You should have read the previous parts of the series before coming here, as this is a continuation.

A collection is an array, a set or a map. I use a map for illustration. A similar analysis can be used for an array or set. The map is created from a two dimensional array.

Initial Data
The initial data for the map is the following fruit/color data:

Apple, purple
Banana, yellow
Pear, green

Map Creation
The following code creates the map:

    mapObj = new Map();

    mapObj.set('Apple ', "purple");
    mapObj.set('Banana', "yellow");
    mapObj.set('Pear', "green");

Problem
The problem with a collection is that the values of the elements can be deleted, changed and the number of elements can be increased.

Solution
As of now, there is no official way to keep the values of a collection, fixed (locked). The fundamental solution is to re-code all the key/value pairs in constant statements as follows:

const Apple = "purple";
const Banana = "yellow";
const Pear = "green";

That is it for this part of the series. We stop here and continue in the next part.

Chrys

Broad Network

Related Articles

ECMAScript Collection Insecurities and Prevention

ECMAScript Insecurities and Prevention – Part 4

ECMAScript 6

Introduction

Related Links

Comments