Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[no-undef] False positive for Interfaces #342

Copy link
Copy link
Closed
@dawsonc623

Description

@dawsonc623
Issue body actions

Repro

Paste the below code into a file and lint it.

interface StringCollection
{
  get(
    index : number
  ) : string;
}

export default StringCollection;

Expected Result

ESLint should not produce any errors

Actual Result

ESLint produces a no-undef error.

Additional Info

Oddly, it also complains about me using new Map<T, U>() with the same rule. I am not sure if it is the same root cause, but I figured it was worth noting.

Versions

package version
@typescript-eslint/eslint-plugin 1.4.2
@typescript-eslint/parser 1.4.2
TypeScript 3.3.3333
ESLint 5.15.1
node 8.15.0
npm* 6.4.1
yarn* 1.12.3

* I use Yarn instead of NPM

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingSomething isn't workingpackage: eslint-pluginIssues related to @typescript-eslint/eslint-pluginIssues related to @typescript-eslint/eslint-pluginscope analyserIssues that are caused by bugs/incomplete cases in the scope analyserIssues that are caused by bugs/incomplete cases in the scope analyser

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.