Lucas Hosseini

@mihaimuntenas Thanks for reporting this – it should be fixed by using master (`gem 'jsonapi-hanami', github: 'jsonapi-rb/jsonapi-hanami'`). I'll try to publish the new version soon.

@Quintasan Yes, definitely. It wouldn't take much work, as @dawidof is already maintaining the base gems, so it would just be a matter of maintaining the Hanami integration. Please shoot...

This project is not dead but I currently have limited time to maintain it.

This clearly needs proper docs, I agree. In general, the idea is that one defines a custom deserializable resource as @hectorsq explained, using the DSL. In `jsonapi-rails`, there is a...

@hectorsq: Thinking about your issue, it is really weird that you do get an `:observation` param added at all if [this line](https://github.com/jsonapi-rb/jsonapi-rails/blob/master/lib/jsonapi/rails/controller/deserialization.rb#L68) is not being executed as you mentioned. 🤔

> Anyone cal tell me the best alternative to jsonapi-rails Valid alternatives, with their own issues: jsonapi-serializers, jsonapi-resources. > as it clearly fails when it comes to deserialization. Nothing is...

Thanks for the PR! I'll leave the decision to @remear, but in the meantime here is one remark about your third point ("Support for deserialization using a custom Deserializer for...

This has been on my radar for a while, but I'll wait until sideposting is fully spec'ed before changing the lib.

Hi @samnang – you are right. There is a fix for Rails 5 in https://github.com/jsonapi-rb/jsonapi-rails/pull/70, and I'll try to cut new releases of all gems next week. In the meantime,...

Hi @samnang > When I render a resource that includes relationships, are nested relationships required to override cache key, or we just only define in top/root resource only? Not sure...