Skip to content
This repository was archived by the owner on Jan 19, 2019. It is now read-only.

Problem with Interfaces #75

Closed
gaurav21r opened this issue Aug 30, 2016 · 2 comments
Closed

Problem with Interfaces #75

gaurav21r opened this issue Aug 30, 2016 · 2 comments
Labels

Comments

@gaurav21r
Copy link

What version of TypeScript are you using? 1.8.10

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

What code were you trying to parse?

interface Iwhen {
  (config: Object, thenFunc: Function): any,
  _eventHandlers: Object,
  _attributeHandlers: Array <Object>,
  _propertyListeners: Array <Object>,
  _mutationObserver: MutationObserver
}

.eslintrc

{
  "extends": "airbnb",
  "parser": "typescript-eslint-parser"
}

What did you expect to happen?
From what I could gather from #74 , I should be able to get Linted with no Errors

What happened?

  1:11  error  'Iwhen' is not defined               no-undef
  3:4   error  'config' is not defined              no-undef
  3:20  error  'thenFunc' is not defined            no-undef
  4:3   error  '_eventHandlers' is not defined      no-undef
  5:3   error  '_attributeHandlers' is not defined  no-undef
  6:3   error  '_propertyListeners' is not defined  no-undef
  7:3   error  '_mutationObserver' is not defined   no-undef
  7:22  error  'MutationObserver' is not defined    no-undef

@platinumazure
Copy link
Member

I did say "when this project is ready". 😄

I don't know if we've even gotten to interfaces yet.

@nzakas
Copy link
Member

nzakas commented Aug 30, 2016

@gaurav21r I appreciate the enthusiasm, but please note what it says on the readme:

Reporting Bugs

Do not file bugs about ESLint rule failures. This is expected because ESLint doesn't know anything about TypeScript syntax. It's likely that many ESLint rules will have failures as a result. Longer-term, it's likely we'll need to create a custom set of ESLint rules that are TypeScript-specific.

Bugs should be filed for:

  1. TypeScript syntax that fails to parse.
  2. TypeScript syntax that produces an unexpected AST.

We are still very far away from having all ESLint rules work, and from having ESLint know how to interpret TypeScript-specific syntax.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants