News for hackers. Stuff that matters.
Re:Introducing the Rails API Project by tomblomfield on Thursday November 22, 2012 @07:09PM (#4820501)
This looks great - I'll be trying it out for a project this week.

I'm still searching around for a good solution to API "views" or presenters when I don't want to expose all of a model's attributes. Something like Rabl? What do other people use?

Re:Introducing the Rails API Project by steveklabnik2 on Thursday November 22, 2012 @07:31PM (#4820552)
The organization includes ActiveModel::Serializers, which is really important for giving you normalized JavaScript output. Rabl is slow and manual, which is the opposite of the Rails philosophy. Convention over Configuration wins every time.
Re:Introducing the Rails API Project by tomblomfield on Friday November 23, 2012 @05:33AM (#4821737)
ActiveModel::Serializers is exactly what I was looking for, thanks!
Re:Introducing the Rails API Project by joecorcoran on Friday November 23, 2012 @05:03AM (#4821660)
Hi Tom, we've been using a combination of responders and Draper decorators for this. It has been in production for almost a year and has worked out pretty well so far. Simon, one of our developers, wrote a couple of articles outlining our API setup:

Part 1: http://techblog.tribesports.com/blog/2011/09/24/versioning-t... Part 2: http://techblog.tribesports.com/blog/2011/09/24/separating-a...

Re:Introducing the Rails API Project by mihar on Thursday November 22, 2012 @07:20PM (#4820531)
RABL is very good at this.