`expiring-todo-comments`: failing the lint on a date may be inconvenient

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

Contributor guide

Research direction

Review the referenced pull request #1540 and the current implementation of the expiring todo comments rule. Propose a modification to allow configuration of whether to fail on expiration date or only warn.

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.

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

GitNode.js

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

65