he/him 
First impressions with TypeScript: - Docs for tsconfig.json are confusing. Why are type checking options under compilerOptions? - The "An import path cannot end in .ts" rule not being optional is maddening
Show this thread
-
Does TypeScript have object type spreads? In Flow I can do: type a = {a: string}; type b = {b: string}; type c = {...a, ...b};
Show this thread
Is there any way I can get vscode to show errors for *all* files, not just the ones I open?
-
-
-
My code is so malformed that it actually caused TypeScript to fail. Impressed and shocked at myself.
Show this thread
End of conversation
New conversation -
-
-
If anyone wants to do this, then feel free to use my hack... $ tsc --noEmit | grep ".ts(" | cut -f1 -d"(" | uniq | xargs code
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I usually add a `“problems”: “tsc --noEmit”` to my package.json
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Best I’ve found is `tsc --noEmit` although maybe the Problems tab might be a thing here
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Add a build task and a problem matcher. Thats what you are looking for.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This one is extra annoying You have to set up a build task that runs tsc on your whole project and then scans the output with a problem matcherhttps://code.visualstudio.com/Docs/editor/tasks#_processing-task-output-with-problem-matchers …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.