jbuilder vs active model serializers

[camallen]

I think we should use active model serializers.
Thoughts?

[edpaget]

I spent some time this morning looking at various Rails serialization libraries. It looks like there are two that seem to have advantages over ActiveModel::Serializers.

• RestPack::Serializer seems like it is more up-to-date with the JSON API spec that AMS also implements.
• Oat looks like it offers more flexibility in terms of output formats.

@brian-c does going with something JSON API based sound good to you? I'll start converting the Apiary stuff I've written to look like that instead.

[brian-c]

JSON API looks sweet. Is the idea that everything is returned in a list by its type, and then referenced by its ID under the links key so nothing is nested? That'll make it super easy to manage model instances in the browser. This is kinda amazing.

[parrish]

I'm both in favor of JSON API and RestPack.
RestPack also looks like a much cleaner/less wacky implementation than Oat

[edpaget]

Great I'll start updating the apiary docs I'm writing to look like JSON API
On Jun 2, 2014 11:36 AM, "Michael Parrish" notifications@github.com wrote:

I'm both in favor of JSON API and RestPack.
RestPack also looks like a much cleaner/less wacky implementation than Oat

—
Reply to this email directly or view it on GitHub
#13 (comment).

[camallen]

A bit late but I prefer the JSON API format. RestPack::Serializer looks good to use and comes with paging built in. Nice find Ed!