4 ms·
And then you have to contribute to a codebase with restrictive ESLint (bleurgh!) configuration, so you can't even try out whether your code works because the to
by kuramitropolis 4y ago
And then you have to contribute to a codebase with restrictive ESLint (bleurgh!) configuration, so you can't even try out whether your code works because the tooling disallows you from compiling it as long as it contains "any", and the other devs are like "but muh best practices". So not only you gotta work around TS, you gotta do it invisibly. How did people even live before VSCode's type hint popups covered up the previous line?
- wiseowise 4y ago> How did people even live before VSCode's type hint popups covered up the previous line? Same. Like normal people do when they use Visual Studio/IntelliJ/QTCreator
- kuramitropolis 4y agoI.e. cringing all the time?
- wiseowise 4y agoCringing at compile time safety or what?
- kuramitropolis 4y agoNo, cringing at some "helpful" popup appearing right over the previous line of code. If anything, they could've made it appear under the current line; code's still written top to bottom so it's less likely for "suggested relevant info" to obscure the actual relevant info.
- Tyriar 4y agoYou can press f8 to view the problem in a "peek view" under the problem line, or view on the problems panel.
- kuramitropolis 4y ago> 10542667 Aug 9 20:40 node_modules/typescript/lib/typescript.js aint fitting ten megs in a peek view... :(
- xodeus 4y agoThis comment has just triggered my PTSD from every Typescript project I've had to work on.