Clarification on returning array vs object for an individual resource #268
Description
From #237, a breaking change to how we should return individual resources was accepted.
Previously, we always returned an array for ease of processing. I realize it's from a year ago, but in #8, it seemed like "always return an array" was the accepted thinking.
BREAKING CHANGE: Singular resource objects SHOULD now be be represented with
JSON objects instead of arrays. This allows for symmetrical representations in
request and response documents, as well as PUT/POST requests and PATCH
operations. It also simplifies implementations which do not support batch
operations (i.e. they can allow an object and not an array).
This was the explanation and it seemed like there was scattered discussion within #237, but I haven't seen rationale as to why this change was accepted/desired?