SetToOneReferenceID called with wrong name when multiple foreign keys to same type about api2go HOT 4 CLOSED

Given that IsNotLoaded fixed my issue, and is the thing that drives omission of the "data":[] element, I think this is not a bug.

from api2go.

I've isolated this problem. I am using jsonapi.Marshal to generate JSONAPI style of JSON that I am POSTing via REST. Marshal collapses "data":[] elements.

However, on the receiving end, JSONAPI has a malfunction when these nested data elements are not present.

So back to my example above, I had to modify the POSTed json to replace "deleted-comments": {} with "deleted-comments: {"data":[]}. And that then allowed the other relations to get processed.

Another work-around a colleague of mine just found is to selectively publish a different schema (GetReferences()) if no foreign key values exist. But the client then loses the ability to see the schema, to know how to offer create options for related data, which is not exactly in the spirit of JSONAPI links.

from api2go.

Fixed by setting Reference IsNotLoaded: false.

from api2go.

Hm, we should definitly look further into this and at least add a test case to our unit tests to make sure this works.

Can you paste some example jsons that you also tried it out with as a reference as well? Thanks so far already!

from api2go.