Oleksiy Babich

To my understanding only index-related keys should be touched Also, LUA scripts should provide support for save actions

I think it is more important to tag "relation", not model I will scan all multi-keys operations for possible issues

@shishirmk I think the only thing needed from the gem is to be able to define root key as `"errors"` instead of `"data"`, etc. Errors themselves look just like a...

If you do not serialize all the chain - client will not be able to restore the chain in general use case I think making docs more clear about this...

even basic requirements are missing here :) what is auth here? auth for humans? auth for APIs? and this is only beginning of long question/decision tree about how auth _may_...

https://github.com/fotinakis/jsonapi-serializers/blob/master/lib/jsonapi-serializers/serializer.rb#L115 https://github.com/fotinakis/jsonapi-serializers/blob/master/lib/jsonapi-serializers/serializer.rb#L150 I see an issue in these lines: lets take an example above `/get/posts?include=comment.author` in lines above default `inslude_data` is `false` and `@_include_linkages` never has `comment` match this means...

My immediate impression is that `include_data` should be defaulted to `true`, why not?

You need to follow JSONAPI specs http://jsonapi.org/format/#fetching-sparse-fieldsets Spec means that you always return the widest available/defined fieldset, and client **MAY** shrink list of required fields, but **DOES NOT HAVE TO**...

Can you please provide more details what you expect here? For me behavior of block attributes is very predictable I'm just asking for clear explanation what you want: get true/false...

Interesting issue, but without failing spec it's hard to "fix" Or you can already do some specs?