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

Description

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

Contributor guide

Tech stack

javascriptnodejs

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.

half day

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

stale

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

mostly clear

Prerequisites

JavaScriptESLint plugin basicsFlow type annotations

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

40

Research direction

The issue reports that ESLint's no redeclare rule incorrectly fires for Flow declare function overloads. The root cause may be in the no redeclare rule implementation within eslint plugin flowtype. To fix, examine the rule's source code (likely in src/rules/no redeclare.js) and understand how it detects redeclarations. The related babel plugin issue (https://github.com/babel/eslint plugin babel/issues/162) provides a similar fix for Babel's parser. The solution likely involves ignoring declare function overloads that are valid Flow syntax. Testing with the provided code snippet should validate the fix.