Forum - Changes concerning the handling of null values

  • This topic has 0 replies, 1 voice, and was last updated 1 week, 1 day ago by Marc Zobrist.
Viewing 1 post (of 1 total)
  • Author
    Posts
  • #76176
    Marc Zobrist
    Participant

    I observe slight changes in the behavior of various endpoints concerning how fields containing no values are handled. While earlier the «Retrieve Representations» endpoint returned no «representation» key if there were no representations for a specific mms_ID, now the response contains always this key, associated with a null value.
    {“representation”:null,”total_record_count”:0}
    This behavior changes go even further. If one of the representations is not associated with a specific «entity_type», this key is nevertheless present in the response, associated with a «null» value. These changes pertain only to the JSON responses, while the XML responses are not affected. The result is that now the JSON and XML responses differ concerning the sets of keys returned for the same request.

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.