Support different collection resource objects

[ianqueue]

Feature Request

Support different object structures within a collection resource endpoint.

What is the expected behavior?

One would be able to create different object payloads randomly or programmatically that would produce something like the following...

[{
  "id": 1,
  "color": "red"
},
{
  "id": 2,
  "shape": "square"
},
{
  "id": 3,
  "size": 100
},
...
]

Having a simply null for unused properties is not always ideal as your resource may describe a collection of fundamentally different "things".

Which version of golang, and which browser and OS does this issue affect?

go version go1.8 darwin/amd64