Does not support objects in an array about json-api HOT 1 OPEN

So, there are two distinct things going on here.

The first is that the json-api library is trying to read your schema to automatically generate documentation, and, as you suggest, it's having trouble with arrays of embedded objects. That's definitely a bug/missing feature, and I'll keep this issue open as a reminder to add it.

But there's a deeper problem here, which is that the JSON API specification, which this library merely implements, doesn't (yet) support nesting data in the way you're trying to do. Here's the relevant paragraph from the spec:

Complex data structures involving JSON objects and arrays are allowed as attribute values. However, any object that constitutes or is contained in an attribute MUST NOT contain a relationships or links member, as those members are reserved by this specification for future use.

In other words, having a messages attribute that holds an array of objects is ok, but those objects can't have a relationship to other model(s), so the author relationship to User is impossible.

There has been much discussion about allowing relationships in object attributes, and it may well happen—but not for at least a few months. These spec things move slowly, unfortunately.

For now, therefore, I'd suggest making message into it's own model, and having message contain a relationship to the discussion that owns it (or vice-versa). Then everything will work smoothly with this library and the specification.

from json-api.