jherr

Frameworks like React require that when you change the contents of an array or object you change its reference. Or push another way that you don't change arrays but instead create new arrays with updated values (i.e. immutability).

There are older array methods that are incompatible with immutability because they alter the array in place and don't change the array reference. These are mutable (or destructive) methods.

Shown below are replacements for the array destructive methods (e.g. push, pop, splice, sort, etc.) that will create new array references with the updated data.

Solutions are provided using the spread operator and also the newer "change array by copy" methods (toSpliced, toSorted, toReversed and with).

Setting Value At Index

ryanfitzer

/**
 * Check for common keyboard actions.
 *
 * @example
 *      checkInputType( e, 'shift click', fn );
 *      checkInputType( e, [ 'escape', 'enter' ], fn );
 *      checkInputType( e, [ 'tab', 'shift tab' ], fn );
 *
 * @param {Event} e - The event object.
 * @param {String|Array} types - The name(s) of the inputs to check.

bigsergey

Review checklist

General

1. Does the code work?
2. Description of the project status is included.
3. Code is easily understand.
4. Code is written following the coding standarts/guidelines (React in our case).
5. Code is in sync with existing code patterns/technologies.
6. DRY. Is the same code duplicated more than twice?