overloading a function using declare is producing ESLint no-redeclare error

Repository metrics

Stars

1,069 stars (1,069 stars)

PR merge metrics

No merged PRs in 30d (No merged PRs in 30d)

Description

declare function DataPoolConnectMethodType (): Promise<DatabasePoolConnectionType>;
declare function DataPoolConnectMethodType ((connection: DatabaseIsolatedPoolConnectionType) => Promise<void>): Promise<void>;

Contributor guide

Research direction

Investigate how Flow's declare function overloads are parsed and how the no redeclare rule handles them. Look at the ESLint no redeclare rule source and the Flow parser or plugin for ESLint. Consider if the issue is in the parser or in the rule logic. Check the related issue babel/eslint plugin babel#162 for prior work.

Tech stack

javascript

Domain

toolingdeveloper experience

Issue type

Bug

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

ESLintFlowTypeNode.js

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

70