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.