Rename Serializer subclasses to Serialization

[bf4]

ref:

• joaomdmoura@0d2ef9a
• WIP - Deserializer implementation #950 (comment)
• Fix the build
• Discuss naming of files and superclasses, esp with respect to https://github.com/rails/rails/blob/4-2-stable/activemodel/lib/active_model/serialization.rb

[bf4]

hmm

[beauby]

I am not too sure about this change personally. I like that in a rails project I have my controllers in app/controllers/ and my serializers in app/serializers. It would be weird to have "serializations" in app/serializers and even weirder to have them in app/serializations.
I agree the name "serializer" is not perfect, but at this point I'm afraid we're kinda stuck with it.

[NullVoxPopuli]

I don't like the name change. Serializer leads us to believe that the class is something that can serialize. Serialization makes it sound like it is data that is already serialized, imo.

[beauby]

@NullVoxPopuli Thing is, our "serializers" do not actually "serialize" anything, they merely present the objects in an adapter-friendly way.

[NullVoxPopuli]

So then I guess Hasherizer may be more appropriate? :-)

[beauby]

Or SerializationPresenter, but in any case, the project is called ActiveModel::Serializers so we kinda have to stick with Serializers in my opinion.

[NullVoxPopuli]

how strongly does rails feel about "Serialization"? it looks like they just have the one module https://github.com/rails/rails/blob/4-2-stable/activemodel/lib/active_model/serialization.rb

[bf4]

This has been rejected...