Nino

no worries ;) thx!

Although I really like [pkg/errors](https://godoc.org/github.com/pkg/errors) I am not sure if a library like api2go should force such a framework onto the user, even if its small and helpful. I think...

yes we stopped working on that project. But it could be that api2go is still in use there :)

There was a draft for a bulk extension IIRC https://github.com/json-api/json-api/blob/9c7a03dbc37f80f6ca81b16d444c960e96dd7a57/extensions/index.md But they are in the process of rewriting this so no support at the moment... There is always the possibility...

The specification of jsonapi only specifies 200 for OK and 404 for not found. http://jsonapi.org/format/#fetching-resources Could you describe your problem a little bit?

Regardless of wether it is a bug or a feature, the next problem will be to implement the "see other" location header. But I'm working on it. If you can...

@tochiai I implemented most of the basics in #244 if you want you can test it. But its not yet possible to perfectly implement it.

yeah that would be awesome. Also I agree, it has to work with the routers. But BC breaks are not that problematic at the moment.

thank you! Much appreciated!

In order to reduce the duplication you could also make use of embedding: [Playlink](https://play.golang.org/p/5iKMLMeO0DY) ``` package main import ( "encoding/json" "fmt" ) type Api2go struct { SharedField string ForeignKey string...