Meme transcription: Panel 1. Two images of JSON, one is the empty object, one is an object in which the key name maps to the value null. Caption: “Corporate needs you to find the difference between this picture and this picture”

Panel 2. The Java backend dev answers, “They’re the same picture.”

  • expr@programming.dev
    link
    fedilink
    arrow-up
    7
    ·
    3 days ago

    Only if using JSON merge patch, and that’s the only time it’s acceptable. But JSON patch should be preferred over JSON merge patch anyway.

    Servers should accept both null and undefined for normal request bodies, and clients should treat both as the same in responses. API designers should not give each bespoke semantics.

    • masterspace@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      3
      ·
      3 days ago

      Why?

      Because Java struggles with basic things?

      It’s absurd to send that much data on every patch request, to express no more information, but just to appease the shittiness of Java.