Ben Bieker

Hi, this should work, however the example is very basic and I haven't implemented that in the code. I will try to add this feature in the example and extend...

I found the problem in our examples. As expected I just made a mistake. When reference IDs are in the payload, the `SetToManyReferenceIDs` and `SetToOneReferenceID` depending on the reference should...

ah, now I understand what you mean. You want to create the user and new referenced data in one request. So one user and 2 chocolate datasets. Hmm. Are you...

api2go cannot do that for now. Unmarshaling is only working with IDs. One other problem we have is how we manage the IDs of the new chocolates. The `included` section...

Thanks for asking and your interest in this project. Unfortunately we are not actively maintaining this project anymore. Back when we started it, it was created out of a necessity...

As I already said: I will continue to respond to issues or do PR reviews. Just not actively developing it. Also if you find a bug then open an issue...

Hi, a top level links object is currently used if you use our rest api and not the marshaller standalone. We have another ticket for links here #99 What other...

The reason for pagination to be implemented in the routing/api layer was that we wanted to make it as simple as possible. I think for the standalone marshaller it would...

I am thinking about a good solution for this. It is very easy to achieve a toplevel `links` or toplevel `meta` object that is included in the marshaled result. For...

for the relationship stuff: we could put it into `Reference` https://github.com/manyminds/api2go/blob/master/jsonapi/marshal.go#L32 ``` go type Reference struct { Type string Name string Meta map[string]interface{} IsNotLoaded bool } ```