double included fields about roar-jsonapi

[bencallaway]

@twiduch is correct. There should only be one included section for the purposes of not duplicating resources. It is mentioned under the top level and compound documents sections of the spec. Likewise it is only allowed as a top level property in the JSON Schema (http://jsonapi.org/schema - line 27).

[phortx]

For me this is a problem due to the fact that my API consuming frontend lib can't (and shouldn't) handle multiple/nested included fields.

Is there a way to workaround this bug? Will this be fixed in the near future?

[myabc]

@twiduch I'm trying to find where in the JSON API docs this behaviour is specified :)

I think that in Json API there should be only one included field

What would your expected behaviour be? That only the first-level of an object tree is included? - Or that the tree is flattened to still allow for side-loading of an entire object graph?

[twiduch]

I believe that objects can be nested, but only one included top-level field. The reason is not to repeat same objects.

If User has Roles and User has Friends (of type User). Friends have also Roles.
Than you have Roles repeated in different included statement.

There should be relationships nested with type and id. All those objects should be referenced in top-level included

That is my understanding of spec