Disable warning for TypeScript file not within `tsconfig.json`

I would love to be able to write and run my tests using typescript-node, which works perfectly, except atom-typescript continues to warn my to check if it should be in the files array. This wouldn’t be a big deal, except it then disable completion and linting for the rest of the file. Can we not consider any tsconfig.json in the current directory upward part of the configuration automatically?

I imagine you can run into a similar casing when compiling TypeScript within a Browserify/Webpack/etc. project since you don’t need to define the files for it to work there.

[MrHen]

I would also like a way to disable this warning. I have two scenarios where I want this:

• Running tests using mocha --require ts-node/register
• Using a gulpfile.ts (also with ts-node)

I explicitly don’t want atom-typescript to build these files so I choose not to add them in my tsconfig.json’s filesGlob.

My workaround for the test files was to just throw them away after the build was over but gulpfile.ts lives at the root level and my tsconfig.json has both rootDir and outDir set to something lower than the root.

I am reluctant to modify my tsconfig.json simply to keep an error from appearing in atom-typescript. I would like a way to disable this warning entirely or at least add a way to disable it for a particular file.

[guncha]

I’m closing this since the original issue isn’t an issue anymore. No warnings are generated in the case you’re editing a file that’s not part of a project. The status bar will look something like this:

@demisx what you’re trying to accomplish could be done using a Typescript language service plugin feature that recently landed in 2.3.0. It’s not well documented, but they idea is that you’re able to intercept calls to getDiagnostics and, in your case, filter out messages based on a file and diagnostic type. If someone implements a plugin like that, it will immediately work in atom-typescript, VSCode, SublimeText and other editors that use tsserver, which is why I think this shouldn’t be a part of atom-typescript.