Hi JS twitter -- I want to know what snags you hit the last time you converted a big JS project to TS. No typings for dependencies? Too many errors? Complex build setup? Something else? If you've never done JS->TS, let me know too. New projects in TS? Never touched TS?
-
For us, the main problem was our low level components. You could not properly type new features, because they would use still untyped low level components. These where often so complex that our juniors could not convert them, so they used any or stayed on JS.
Did those components also need to be converted to TS or would you have been OK with adding types in a d.ts file and just leaving them as JS?
-
-
Actually, we started everything by adding tsdoc comments to the components, which serves a similar purpose. The actual Problem appeared when working with generic components, which cannot by typed property with tsdoc.
-
You can use the `@template` JSDoc tag to do that, see:https://github.com/Microsoft/TypeScript/wiki/JSDoc-support-in-JavaScript#template …
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.