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
-
-
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 -
-
-
Didn’t Flow add type c = {...a, ...b} because type c = a & b was not working consistently/as expected?
-
Not really. You don't want a union of colliding properties, you would want the later spread to overwrite previous properties, just like regular object spread.
- 1 more reply
New conversation -
-
-
type C = a & b
-
That's not the same. type A = { a: void | string }; type B = { a: string }; type AB = A & B; Will result in {a: void | string} when I actually want {a: string} which is what you'd get with {...A, ...B}
- 3 more replies
New conversation -
-
-
Object type spreads and opaque type aliases are two of the main Flow features I miss when using TypeScript. On the other hand,
@bcherny's TypeScript book helped me realize that there's a lot of advanced stuff in TypeScript that doesn't exist in Flow. -
Having to write `throw new Error()` instead of just using Flow's magic `invariant()` has been another thing making it more painful
End of conversation
New conversation -
-
-
Yes it has spreads :)
-
It has object spread. It does not have object type spread.
- 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.
he/him 