• ryannathans@aussie.zone
    link
    fedilink
    arrow-up
    1
    arrow-down
    13
    ·
    edit-2
    1 year ago

    But if your code ever integrates with javascript you still need any everywhere so it’s pretty pointless

    • 9point6@lemmy.world
      link
      fedilink
      arrow-up
      12
      ·
      edit-2
      1 year ago

      Not true, in the absolute worst case, unknown is what you should be reaching for, but it’s pretty rare that you can’t create some kind of type to interface with JS if it’s not already got types. You can even use jsdoc comments as type hints in the JS too if you own that code.

      My not particularly hot hot-take: There’s basically no legitimate use case for any apart from “I don’t have time to type all this now, because I’m converting a massive project from JS to TS”

      • jana@leminal.space
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        There are some cases where any must be used instead of unknown but they usually involve generic constraints and seem more like a bug than intended behavior

    • alokir@lemmy.world
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      Not necessarily, depending on your situation you can type the JS code yourself.

      If the team making the JS code were using jsdoc then the Typescript compiler can recognize the comments and use it for type checking.

      In some instances the compiler can infer types from JS code to do some basic validation.

      Even if the external JS code is recognized as any, your own code that’s using it still has types, so it’s better than nothing.