-
Notifications
You must be signed in to change notification settings - Fork 72
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
Comments
It seems tsuquyomi does not read |
After some more digging, it seems to be due to neomake, not tsuquyomi. Sorry for the noise! Cheers |
@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... |
Hmm, not seeing this in my test. Are you using syntastic? |
I found a workaround, see leafgarland/typescript-vim#47 EDIT: You only have to set this in vimrc file: let g:syntastic_typescript_tsc_fname = '' |
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 :( |
@mhartington: could you elaborate on your digging? just wanna make sure i don't have the same problem |
@chapati23 Have you figured it out? @metal3d I have the same problem, setting |
@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 :-/ |
Hey there. So it seems that in my current projects tsconfig is being ignored for a project
Any time I use an experimental decorator, I get a warning, even though I have the compiler option for decorators enabled. Any ideas?
The text was updated successfully, but these errors were encountered: