Programmer Humor

32563 readers

590 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

327

Me, migrating my code from JavaScript to TypeScript: (lemmy.world)

submitted 1 year ago by callmepk@lemmy.world to c/programmerhumor@lemmy.ml

30 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] xmunk@sh.itjust.works 3 points 1 year ago (1 children)

I don't follow, stamping every function with : any lets you merge the branch and deploy it... trying to properly type everything extends the initial migration time likely to a level where management just says no.

[–] folkrav@lemmy.world 7 points 1 year ago* (last edited 1 year ago) (1 children)

Use a combination of allowJs and ts-ignore, do progressive enhancement, and convert your codebase file by file. Adding any everywhere literally turns off type checking altogether codebase wide, including type inference. It also means a huge PR that's both just noise that needs to be fixed later, and messes with your git history (good luck getting anything useful out of blame or bisect now).

Just getting a green build doesn't mean things are okay. You're worse off than before doing that.

[–] xmunk@sh.itjust.works 4 points 1 year ago* (last edited 1 year ago)

I disagree that you're worse off (the core of my comment was that even a shitty migration encourages better practices)... but I wasn't super familiar with TS hinting - using ts-ignore would be preferable.

Personally, I mostly work in PHP and we use a similar system. Strict typing is default off so we've slowly propagated declare(strict_types=1); to enable compile and runtime checking on a per file basis.