OKURA Masafumi

There are a few reasons, but the biggest one is the fact that there are so many gems out there such as [jsonapi-serializers](https://github.com/jsonapi-serializer/jsonapi-serializer) and [jsonapi-resources](https://github.com/cerebris/jsonapi-resources). I don't think Alba has...

If Alba supports JSON:API, it becomes easier to implement different styles of APIs (JSON:API compatible one and flat one) with only Alba. This could be a killer feature for some....

Hi, I'd like to mention a few things. It's absolutely fine to remove `jsonapi-serializer` from the benchmark, but what do you think about using it to generate non-jsonapi style output?...

Hi everyone in this thread, I found it pretty hard to implement this feature. I create a "help wanted" discussion in #217 so if you really want to add JSON:API...

@trevorturk I came up with the following code: ```ruby class AnotherUserResource include Alba::Resource transform_keys :lower_camel, cascade: true #

Making cascade default seems reasonable to me. Yes, it's a breaking change, so we need to offer a `cascade: false` option for old behavior. Unfortunately it's hard to produce deprecation...

@lukaspili Hi, it's currently not possible but if there're some usecases I'd like to support it. Could you share your usecase? For example, what kind of JSON output you want...

One way to achieve this goal would be to use inheritance, for example: ```ruby class UserJson include Alba::Resource attributes :email_address end class AnonUserJson < UserJson def attributes super.reject {|k, v|...

True. Would you implement this feature on your own? If you will I can help. If not, then don't worry, I'll implement it.

I found no `segfault` in dmesg output.