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.