ActiveModel::Serializers VS Blueprinter

Hey folks, I've been using FastJsonapi::ObjectSerializer in past projects, but it is now deprecated and it's successor is "in maintenance mode! ". The og serializer had no release since 2015.

Further reading: Active Model Serializers Github

In order to use our serializers, first we must install the gem into our gem file. we can do that by first grabbing our "Active Model Serializers" gem file from "https://rubygems.org/gems/active_model_serializers/versions/0.10.13". We will copy the gem from this website and paste it into our gem file in our application like so

Today I thought I'd run through a few of the powerful things that the ActiveModel::Serializer gem brings to the table when used in a Ruby on Rails application. Sure, there are faster alternatives, but AMS is the first one I learned how to use, and thus it holds a special place in my heart. Quick question before we dive too much deeper, though...

AMS

ActiveModelSerializers to build JSON views

Might be overkill for your situation but I generally use https://github.com/rails-api/active_model_serializers for my projects. Otherwise just build the hash you are sending back to the frontend with standard code.

On the other hand, we have Active Model Serializers. This gem is also deprecated but has another stable version 0.10. I also found Blueprinter gem. I've never used it before and don't know its limitations.

Blueprinter is something we use on a project, it's also having difficulty staying alive, but right now there is active development here, a fork from the original blueprinted gem.

Beware of this

Serializer: procore/blueprinter: Simple, Fast, and Declarative Serialization Library for Ruby

Today I thought I'd run through a few of the powerful things that the ActiveModel::Serializer gem brings to the table when used in a Ruby on Rails application. Sure, there are faster alternatives, but AMS is the first one I learned how to use, and thus it holds a special place in my heart. Quick question before we dive too much deeper, though...

Blueprint

Just an FYI: While I agree that the blueprinter gem is awesome, there are currently no active maintainers: https://github.com/procore/blueprinter/issues/288

In a happy coincidence, we're knee-deep in the middle of a migration of our serialisers to use Blueprinter instead of AMS. One benefit, in this case, is that it lets you explicitly set what generator you're using, like so:

What made me think about this is that I'm using (maybe in the wrong way) some gems like Blueprinter and Amoeba.

I've been using Blueprinter so far, and it has been working great, but I'd like to ditch it if I can.

We use it extensively for one project. The only annoying bit involves defining the response json-schema. Luckily we are using a gem called blueprinter for JSON serialization, so we added a bunch of overrides that store metadata, so we can generate the json-schema with meta programming. You might need to find a library that would help you write the schemas fluently [1] / [2] to make it easier to define them.