Rule proposal: `prefer-change-array-by-copy`

Repository metrics

Stars

5,022 stars (5,022 stars)

PR merge metrics

Avg merge 1d 16h (Avg merge 1d 16h)399 merged PRs in 30d (399 merged PRs in 30d)

Description

array.reverse();

array.sort();

const array = [...foo];
array.splice(0, 1);

const array = [...foo];
array[1] = 'changed';

array = array.toReversed();

array = array.toSorted();

const array = foo.toSpliced(0, 1);

const array = foo.with(1, 'changed');

Contributor guide

Research direction

Implement a new ESLint rule that detects calls to array mutating methods (reverse, sort, splice, index assignment) and suggests using the new non mutating alternatives (toReversed, toSorted, toSpliced, with). Follow the pattern of existing rules in the plugin. Write tests for both fail and pass cases.

Tech stack

javascript

Domain

tooling

Issue type

Feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

JavaScript

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

75