Flow interface incorrectly determined to be undefined

[arv]

Similar to #66 but for interfaces.

// @flow
interface Foo {
  m(): number;
}

export function f(foo: Foo): Foo {
  return foo;
}

$ npm ls babel-eslint
└── babel-eslint@5.0.0

$ node_modules/.bin/eslint foo.js

.../foo.js
  2:11  error  "Foo" is not defined  no-undef
  6:24  error  "Foo" is not defined  no-undef
  6:30  error  "Foo" is not defined  no-undef

✖ 3 problems (3 errors, 0 warnings)

[mechanoid]

Is there any news on that?

[trevorr]

Until this is fixed, this workaround is available: https://github.com/zertosh/eslint-plugin-flow-vars

[hzoo]

https://github.com/babel/babel-eslint#known-issues - This isn't really something we can fix because there are conflicts between no-undef and no-unused-vars. We recommend ^ like in the readme