eslint warning no-use-before-define should not apply to flow types

[wereHamster]

Description

The default eslint rules warn about no-use-before-define of flow types. The warning is pointless because 'use before define' does not apply to flow types. This makes it impossible for example to define recursive types.

Expected behavior

The no-use-before-define warning should not be reported.

Actual behavior

Warning appears in the console.

Reproducible Demo

Create a CRA project and place the following text into one of the files:

type Node = {
  children: Node[];
}

[gaearon]

Please report this to the upstream projects (in this case, maybe babel-eslint or eslint itself). Or perhaps eslint-plugin-flowtype can help with this.

[gaearon]

You can track this in babel/babel-eslint#485. When they fix it, we'll get the fix too. You can also try to help fixing this in babel-eslint repo :-)

[joa]

Submitted a PR. Not really sure if it is the right way ™ since I have no experience with Babel or ESLint but all tests are passing: babel/babel-eslint#584