Rule proposal: `no-unreadable-new-expression`

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

const bar = new Foo().getBar();

const Bar = new Foo().Bar;

const Bar = new (Foo().Bar);

const bar = new foo.Bar();

const bar = (new foo).Bar();

const bar = new foo().Bar();

const bar = new (foo().Bar)();

const foo = new Foo();
const bar = foo.getBar();

const foo = new Foo()
const Bar = foo.Bar;

const {Bar} = foo;
const bar = new Bar();

Contributor guide

Research direction

Implement a new rule in eslint plugin unicorn. See existing rules for patterns. The rule should detect patterns like `new Foo().Bar` and suggest separate statements. Check the repository's rule structure in `rules/` directory and follow the testing and documentation conventions. There are 8 comments with discussion; review them for additional context.

Tech stack

javascript

Domain

developer experiencetooling

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.

Half day

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

Fresh

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

Clear

Prerequisites

Basic understanding of ESLint rulesFamiliarity with AST manipulationKnowledge of JavaScript

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

65