Galooshi/import-js

`export interface` not supported in Flow

Open

#494 opened on Apr 10, 2018

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (519 stars) (70 forks)batch import
enhancementhelp wanted

Description

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

Contributor guide

Tech stack
javascript
Domain
tooling
Issue type
feature
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.
clear
Prerequisites
Flow knowledgeJavaScript parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
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.