I first found this thread and gave Rails enum a shot. It "seemed" to work, but it only did for String mappings. Even if enum was defined, when assigning attributes, jsonb_accessor would update the jsonb with the value from the public getter, which returns the corresponding enum key (whatever that is) and not the actual value that should be stored in the database.

This was first noticed by kg-currenxie.

Example

Given:

jsonb_accessor :data, my_enum_attribute: :integer
enum my_enum_attribute: { "Foo" => 1, "Bar" => 2 }

MyClass.create(my_enum_attribute: "Foo") will store a jsonb with "Foo" as value instead of 1.

With the introduced changes, the actual value stored will be 1.

The use of enums with integers allows a ton of flexibility when it comes to altering existing enum keys. I'm in the middle of a migration and having enums defined with integers instead of strings makes things much easier.