Fix your aversion to type checkers (1) write JS without any type annotations and avoid relying on dynamic features (2) change your code until it works correctly (3) run the type checker and type annotate the code until it passes the checker
-
-
-
10-20% of the type checker errors in (3) are actual bugs that would slip by. This number is much higher when you are refactoring existing code instead of writing it from scratch (1). So step (3) is an investment that will pay off once you or someone else is refactoring the code.
- Još 6 drugih odgovora
Novi razgovor -
-
-
This video had perfect timing. In my job we're trying Typescript to check if it merges nicely into our workflow. It seems like it doesn't, but type inference on js using ts may be the compromise we needed.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Č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.