bf4 said over 7 years ago on Rails API - Active Model Serializer :

I'm here due to the link from RubyWeekly. I haven't watched the video, only seen the notes, but as an ActiveModelSerializers maintainer, I'd ask if the various unusual decisions could be explained and if they should be something the library should handle.  For example: 1) mixing in the url helpers is not necessary 2) the show method in the serializer, besides violating separation of concerns, is very strange, and I'm not sure how it would be used 3) code is missing any configuration