Lucas Hosseini

@bsylvain This should be the case, providing you use jsonapi-rb deserializers. Could you show a minimal example where this fails?

Hi Adam, thanks for the in depth write up. Errors support is indeed largely perfectible. The main issue is that Rails’ ActiveModel doesn’t report errors individually, which breaks the “one...

Thanks for bringing this up. Regarding `source`, it will only work out of the box if you're using `deserializable_resource` to deserialize the input payload. There's room for improvement there, but...

The errors are set by the deserializer, which are independent from the serializers. The `deserializable` module maintains a reverse mapping for renamed keys, which is used to generate the JSON...

@JoeWoodward Yes, I haven't had time to give the love this project deserves, and @dawidof is in charge now. This PR does several things (update TravisCI configuration, jsonapi payload for...

Hi @ZempTime > + set this option inside my controller action? ```ruby render jsonapi: @relationship, class: { 'Relationship::Approve': SerializableRelationship } ``` > + set this option at the controller wide...

@bprotas Yes, you were almost there: the `class` option of the `render` method does that for you, and the default value for the `class` option can be overridden by overriding...

@bprotas I see. The json:api standard is based on the idea of serializing a _graph_ of resources, so the general case is that one needs to map each resource type...

Agreed that the lib should at least raise a custom exception so that people can rescue from it with a sensible json:api error. Would you mind issuing a PR for...

IIRC, the `/data` pointer should always be valid, unless the payload itself is invalid (to be double checked), in which case we could add some logic to craft the right...