Update PORO description

[harlow]

It's not entirely clear how read_attribute_for_serialization is supposed to be implemented. I had to look back at the older README to find the mention of ActiveModel::SerializerSupport.

class Poro
   include ActiveModel::SerializerSupport

   # ...
end

Is there a better way to handle this?

[coveralls]

Coverage remained the same when pulling d92bd15 on harlow:hw-updated-readme into c65d387 on rails-api:master.

[spastorino]

There's no ActiveModel::SerializerSupport anymore. The typical way to implement read_attribute_for_serialization is as an alias to send, but the method is still there in case developers want to decorate what send returns.

[harlow]

@spastorino thanks for the quick reply. Do you mind expanding on that a little more? For example we've been using PORO's for object-graphs that don't have immediate relations between models i.e.:

class Poro
   inculde AciveModel::Model

   def some_array_of_foo_objects
   end

   def some_other_non_related_bar_object
   end

   def read_attribute_for_serialization
     # what goes here?
   end
end

Then a serializer

class PoroSerializer
   has_many :some_array_of_foo_objects
   has_one :some_other_non_related_bar_object
end

Maybe I'm looking at it the wrong way. Let me know if you have some more details on this and I'll get the README updated appropriately.

[spastorino]

You can do ... alias read_attribute_for_serialization send
For more info https://github.com/rails/rails/blob/cc8d1482/activemodel/lib/active_model/serialization.rb#L125-141

[harlow]

Thanks for the note. Closing this as it's not longer relevant.

[mech]

Hi, I include ActiveModel::SerializerSupport because I need the controller to automatically find out where to look for the serializer because of active_model_serializer. If there is no more ActiveModel::SerializerSupport support, may I know how my PORO can let my controller know where to find it automatically rather than using the serializer

respond_with @company, serializer: MySerializerWhichAMSCantFind

[spastorino]

ActiveModel::SerializerSupport is there :)

[stevenharman]

I believe @mech was referring to the old (pre 0.9.0) behavior of ActiveModel::SerializerSupport adding a #serliazer_for method to any object into which it was included. We no longer rely on that an instead rely on a convention of class named Poro using a PoroSerializer.