fhir_client VS Blueprinter

There was no specific place that was causing issues; it seemed to me whenever we were making a request via the client we had set up to hit an external API. Taking a quick trip to the issues for the project turned up an issue that looked suspiciously similar but with no actual outcome at the end of the thread barring some workarounds.

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.