Galooshi/import-js

`export interface` not supported in Flow

Open

#494 建立於 2018年4月10日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)JavaScript (519 star) (70 fork)batch import
enhancementhelp wanted

描述

Flow supports export interface, but importjs doesn't pick up on these statements when auto-importing.

A workaround is to use the same workaround as for older Flow versions:

interface iMyInterface { ... }
export type IMyInterface = iMyInterface

It would be nice if import-js supported the shorter export interface... syntax since Flow now supports it.

cf. https://github.com/facebook/flow/issues/1131

貢獻者指南

技術棧
javascript
領域
tooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Flow knowledgeJavaScript parsing
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
The issue requests support for `export interface` syntax in Flow. import js currently uses a JavaScript parser that may not handle this Flow specific syntax. To implement, look at how the parser (likely babel or a custom one) is configured and how it handles Flow type exports. The issue includes a workaround using `export type IMyInterface = iMyInterface`, which can serve as a reference for the expected behavior. Check the repository's Flow support code and consider updating the parser to recognize `export interface` statements.
`export interface` not supported in Flow · Galooshi/import-js#494 | Good First Issue