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

描述

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

贡献者指南

技术栈

javascriptnodejs

领域

toolingdeveloper experience

议题类型

bug

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

half day

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

stale

清晰度议题是否清楚说明期望改动、验收标准和下一步。

mostly clear

前置要求

JavaScriptESLint plugin basicsFlow type annotations

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

40

研究方向

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.