You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 14, 2019. It is now read-only.
What version of typescript-estree are you using?
master
What code were you trying to parse?
N/A
What did you expect to happen?
N/A
What actually happened?
N/A
Had a thought while I was looking at eslint/typescript-eslint-parser#530. Now that the ESLint-compatibility layer has been separated out, does it make sense to keep the ecmaFeatures option? It looks as though it's only used to enable JSX.
I'm not entirely sure ecmaFeatures makes sense for this package - perhaps we could just add either a jsx: true or enableJSX: true option?
We could always make this backwards compatible, if that's a worry. I'm more than happy to make a PR!
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
What version of TypeScript are you using?
N/A
What version of
typescript-estree
are you using?master
What code were you trying to parse?
N/A
What did you expect to happen?
N/A
What actually happened?
N/A
Had a thought while I was looking at eslint/typescript-eslint-parser#530. Now that the ESLint-compatibility layer has been separated out, does it make sense to keep the
ecmaFeatures
option? It looks as though it's only used to enable JSX.I'm not entirely sure
ecmaFeatures
makes sense for this package - perhaps we could just add either ajsx: true
orenableJSX: true
option?We could always make this backwards compatible, if that's a worry. I'm more than happy to make a PR!
The text was updated successfully, but these errors were encountered: