interface not correctly parsed

[boompig]

What version of TypeScript are you using?

2.4.0

What version of typescript-eslint-parser are you using?
3.0.0

What code were you trying to parse?

import { React } from "react";

interface Props {
    hello: string;
}

class TestView extends React.Component<Props, any> {
    render() {
        return (
            <span>{ this.props.hello }</span>
        );
    }
};

What did you expect to happen?

No errors

What happened?

3:11 error 'Props' is not defined no-undef
4:5 error 'hello' is not defined no-undef

✖ 2 problems (2 errors, 0 warnings)

Is this related to #75?

[soda0289]

This is a duplicate of #179. For this to be fixed we need a way for the the scope analysis tool, used be eslint, to understand interfaces. We have some proposals for a possible solution just need to reach consensus on the next steps.

[JamesHenry]

I think this is actually just a standard no-undef issue @soda0289, the import from React is not relevant to the linting failures. The interface is defined and then used within the same file.

@boompig Please see the known issues https://github.com/eslint/typescript-eslint-parser#known-issues, the easy way to resolve this is to use the TypeScript compiler itself to enforce no-undef behaviour. See my comment here for further info: #77 (comment)