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 }}
Repository navigation
Filter TypeScript errors for selected files #10337
Hi, first of all, thanks for the awesome project. You're doing fantastic work.
I am in the process of gradually moving a codebase to using TypeScript. There are certain compiler options which I want to enable, namely no implicit any and strict null checking, however because I am moving things gradually, I only want to enforce these stricter rules on a subset of TypeScript files.
My solution to this is to wrap the TypeScript compiler, filtering out error messages from no implicit any and strict null checking where the file is not whitelisted as “strict”. For example: microsoft/TypeScript#8855 (comment)
However, I do not want to use such a solution in my project without corresponding feedback in my IDEs.
Is there any way I can wrap the TypeScript compiler used in vscode similarly to how I wrapped the TypeScript compiler in microsoft/TypeScript#8855 (comment)?
Or, perhaps I could use my wrapped compiler and send those errors to vscode instead of using the built in TypeScript errors?
Is there somewhere I can find the code that sends the TypeScript errors to vscode?
I want to achieve this for other plugins in other IDEs too, to suit all the developers in my team, but also because I think this will be useful to other people who are gradually moving their codebase to TypeScript and want to start using some of the stricter compiler options.
Activity
jrieken commentedon Aug 9, 2016
You should be able to use the task framework for that
OliverJAsh commentedon Aug 9, 2016
Do you have any more details? I'm not sure what you are referring to :-)
On Tue, 9 Aug 2016 at 10:18 Johannes Rieken notifications@github.com
wrote:
jrieken commentedon Aug 9, 2016
this one: https://code.visualstudio.com/docs/editor/tasks but dirk knows best
dbaeumer commentedon Apr 26, 2017
Closing issue assuming that the task documentation help addressing this.