IMO, this should not be a valid response JSON. While a little research has told me that the initial JSON spec did not mention "duplicate keys" by name as to whether they're valid, many people tend to agree that it's bad practice at best and completely invalid JSON at worst. I would kindly ask that ?include_channels=true either replace the original channels ID array with the "full" channelsobject array, instead of this weird duplicate key response. Alternatively, you could introduce the field with a different name if consistency with other "server" JSON models is desired.
What happened?
As it says on the tin:
GET /servers/{target}?include_channels=true
will produce JSON similar to the following.IMO, this should not be a valid response JSON. While a little research has told me that the initial JSON spec did not mention "duplicate keys" by name as to whether they're valid, many people tend to agree that it's bad practice at best and completely invalid JSON at worst. I would kindly ask that
?include_channels=true
either replace the originalchannels
ID array with the "full"channels
object array, instead of this weird duplicate key response. Alternatively, you could introduce the field with a different name if consistency with other "server" JSON models is desired.