Meme transcription:

Panel 1: Bilbo Baggins ponders, “After all… why should I care about the difference between int and String?

Panel 2: Bilbo Baggins is revealed to be an API developer. He continues, “JSON is always String, anyways…”

  • VeganPizza69 Ⓥ@lemmy.world
    61·
    1 年前

    It’s the API’s job to validate it either way. As it does that job, it may as well parse the string as an integer.

      • bleistift2@sopuli.xyzOPEnglish
        13·
        1 年前

        Or even funnier: It gets parsed in octal, which does yield a valid zip code. Good luck finding that.

        • kamen@lemmy.world
          3·
          1 年前

          Oof.

          I guess this is one of the reasons that some linters now scream if you don’t provide base when parsing numbers. But then again good luck finding it if it happens internally. Still, I feel like a ZIP should be treated as a string even if it looks like a number.

          • bitfucker@programming.dev
            4·
            1 年前

            Yep. Much like we don’t treat phone numbers like a number. The rule of thumb is that if you don’t do any arithmetic with it, it is not a “number” but numeric.

            • lad@programming.devEnglish
              1·
              1 年前

              Well, we don’t, but every electonic tables software out in the wild on the other hand…

              /j

              Yes, I know that you can force it to become text by prepending ' to the phone, choose an appropriate format for the cells, etc, etc

              The point is that this often requires meddling after the phone gets displayed as something like 3e10