Surely "1337" is the same as 1337, right?
Surely "1337" is the same as 1337, right?
![the background blur](https://sopuli.xyz/pictrs/image/15dcbd6e-ee52-4ecc-bd3b-5f760e4ba844.webp?thumbnail=256&format=webp)
![](https://sopuli.xyz/pictrs/image/15dcbd6e-ee52-4ecc-bd3b-5f760e4ba844.webp?thumbnail=1024&format=webp)
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're viewing a single thread.
All comments
72
comments
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.
7 0 ReplyI refuse to validate data that comes from the backend I specifically develop against.
5 0 Reply
72
comments
Scroll to top