Interface produces no-undef errors

[nickserv]

What version of TypeScript are you using?
2.6.2

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

What code were you trying to parse?

interface Runnable {
  run (): Result
  toString (): string
}

What did you expect to happen?
Pass with no errors.

What happened?

> eslint **/*.{j,t}s


/Users/nick/Repos/purespec/matchers/Runnable.ts
  1:11  error  'Runnable' is not defined  no-undef
  2:3   error  'run' is not defined       no-undef
  2:11  error  'Result' is not defined    no-undef

✖ 3 problems (3 errors, 0 warnings)

[bondom]

Is there workaround for this problem?

[EdGraVill]

This is resolved in #75

[Bessonov]

Unfortunately, #75 isn't resolution.

[JamesHenry]

A custom rule will need to be created in the plugin to handle this. It would be fantastic if one of the people affected by this issue could contribute to it.

[jacob-israel-turner]

Has there been any effort on this? If not, I'd be willing to take a stab - although I have very little experience writing linting rules. Is there somewhere I could look for a good first step?

[amcdnl]

Any updates on this? With the new Babel7 TypeScript support this becomes more interesting.

[itsdouges]

Alternatively you could disable the rule and just use ts compiler settings to error on unused variables?

https://www.typescriptlang.org/docs/handbook/compiler-options.html

--noUnusedLocals --noUnusedParameters

[cooperka]

See comments on similar issue #416 for a few workarounds.

Namely, you can safely disable no-undef for .ts files because TypeScript will fail to compile with undefined vars. The rule is redundant. Full example here: #416 (comment)

module.exports = {
  rules: {
    // ... your js rules ...
  },

  overrides: {
    files: ['**/*.ts'],
    parser: 'typescript-eslint-parser',
    rules: {
      'no-undef': 'off'
    }
  }
}