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
- tsconfig.json changes seem to require a restart of vscode - No `import type` like in Flow is annoying. Bundler needs to be smart and know if imports are only used as types so they don't effect module order.
-
-
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?
Show this thread -
-
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 -
-
-
In what context? `const someObject: { foo: string, bar: string } = { foo: 'yep', bar: 'nah' };` should be valid
End of conversation
New conversation -
-
-
Valid point. `import type` is a really good design decision on Flow's part I wonder if TS could add something like that and give a way to incrementally migrate to it
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Code allows you to restart TSC server via commandlet menu which is less but still disruptive.
-
Shh. It's a secret. No one knows about this command. (I find myself using this a lot)
End of conversation
New conversation -
-
-
I don’t think you need a restart for tsconfig changes usually. And agree 100% on import type!
- 1 more reply
New conversation -
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.