blueprinter | Simple , Fast , and Declarative Serialization Library for Ruby | JSON Processing library

I have a project I'm trying to use ruby 3 (previously running with 2.7.2), but couldn't accomplish it.

After updated my gemfile with the ruby version and ran bundle, I'm receiving this error when trying to access rails c:

I'm trying to use the new alternative for serialization: Blueprinter

How do you handle STI collection where every model is some type of view?

I came up with something like this (saw similar code on AMS github issue):

I'm trying to write my first gem, and want to create one that provides functionality to dry-up serialization. I'm using one gem at the moment and don't foresee any issues with it, but I'd like to be able to add support for multiple serialization gems. The only downside I see is that it would require adding them to the dependancy list and installing them into the project that uses the gem I am writing.

Is there a way, using an initializer, to set the preferred gem that a user might want to use and only install that one and not any of the others?

I'm going to write it without this functionality for now, but in the future, I'd like to make it more robust with the support for multiple gems.

I updated with an install generator that creates an initializer with a default gem listed, along with what I thought would work for dynamically adding the dependency. My test passes, and I am able to bundle install locally without any issue and my gem seems to be working as intended, but when I try to push to gemfury I am now getting an error: