Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False warning of experimentalDecorators #56

Closed
mhartington opened this issue Jan 23, 2016 · 9 comments
Closed

False warning of experimentalDecorators #56

mhartington opened this issue Jan 23, 2016 · 9 comments

Comments

@mhartington
Copy link

Hey there. So it seems that in my current projects tsconfig is being ignored for a project

screen shot 2016-01-23 at 8 14 59 am

screen shot 2016-01-23 at 8 15 10 am

Any time I use an experimental decorator, I get a warning, even though I have the compiler option for decorators enabled. Any ideas?

@delphinus
Copy link

It seems tsuquyomi does not read tsconfig.json. It might be fixed if you place tsconfig.json at upper paths /, /app/, /app/pages/, or /app/pages/page1/.

@mhartington
Copy link
Author

After some more digging, it seems to be due to neomake, not tsuquyomi. Sorry for the noise!

Cheers

@metal3d
Copy link

metal3d commented Feb 29, 2016

@mhartington I've got the same problem. I don't use neomake, I'm using "ng" command to generate my angular2 project and I've got the same warning.

Any idea ?

My tsconfig is:

{
  "compilerOptions": {
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "mapRoot": "",
    "module": "system",
    "moduleResolution": "node",
    "noEmitOnError": true,
    "noImplicitAny": false,
    "outDir": "../dist/",
    "rootDir": ".",
    "sourceMap": true,
    "sourceRoot": "/",
    "target": "es5"
  }
}

Vim is opened where the tsconfig file resides...

@mhartington
Copy link
Author

Hmm, not seeing this in my test. Are you using syntastic?

@metal3d
Copy link

metal3d commented Mar 5, 2016

I found a workaround, see leafgarland/typescript-vim#47
The problem was that syntastic didn't checked typscript.json file

EDIT: You only have to set this in vimrc file:

let g:syntastic_typescript_tsc_fname = ''

@chapati23
Copy link

this workaround does not work for me (using neovim 0.1.4)

no matter where i put my tsconfig.json — tsuquyomi does not seem to pick it up :(

@chapati23
Copy link

@mhartington: could you elaborate on your digging? just wanna make sure i don't have the same problem

@vyorkin
Copy link

vyorkin commented Jun 12, 2016

@chapati23 Have you figured it out? @metal3d I have the same problem, setting let g:syntastic_typescript_tsc_fname = '' doesn't help

@chapati23
Copy link

@vyorkin working for me now. unfortunately i couldn't tell you what change helped at the end because i just reinstalled and refactored my whole neovim installation :-/

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

No branches or pull requests

5 participants