566
Surely "1337" is the same as 1337, right? (sopuli.xyz)
submitted 2 years ago by to c/programmer_humor@programming.dev
113 comments fedilink hide all child comments
 

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…”

you are viewing a single comment's thread
view the rest of the comments
[+] 37 points 2 years ago* (last edited 2 months ago) (2 children)
[deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 15 points 2 years ago (2 children)

    Rust has perfectly fine tools to deal with such issues, namely enums. Of course that cascades through every bit of related code and is a major pain.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 24 points 2 years ago (1 child)

    Sadly it doesn't fix the bad documentation problem. I often don't care that a field is special and either give a string or number. This is fine.

    What is not fine, and which should sentence you to eternal punishment, is to not clearly document it.

    Don't you love when you publish a crate, have tested it on thousands of returned objects, only for the first issue be "field is sometimes null/other type?". You really start questioning everything about the API, and sometimes you'd rather parse it as serde::Value and call it a day.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •