A case not handled by `no-for-loop`

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

/* eslint unicorn/no-for-loop: 2 */

const arr = [];

for (let i = 0, j = arr.length; i < j; i += 1) {
  const element = arr[i];
  console.log(element);
}

Contributor guide

Research direction

Inspect the rule source code in the repository, identify the pattern where the array length is cached in a variable (e.g., `let i = 0, j = arr.length; i < j; i += 1`), and add a new check to detect this pattern in the `no for loop` rule.

Tech stack

javascript

Domain

developer experiencetooling

Issue type

Bug

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

2

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

1-3 hours

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

JavaScriptESLint

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

70