`enum.Enum` serialization strategy

[kdkavanagh]

I'm trying to override Mashurmaro's behavior for serializing any/all enum fields, however it only seems to take effect if I configure the strategy for specific enum types. Is there a way to register/override the behavior for anything inheriting from enum.Enum?

class EnumSerializer(SerializationStrategy):
    def serialize(self, value: enum.Enum):
        return f"{fully_qualified_typename(type(value))}.{value.name}"

    def deserialize(self, value: str) -> enum.Enum:
        module, class_name, variant_name = value.rsplit(".", 2)
        import importlib

        mod = importlib.import_module(module)
        return getattr(mod, class_name)[variant_name]

class MyEnum(enum.Enum):
  A=1
  B=2

@dataclass
class MyClass:
  field_one: MyEnum = MyEnum.A
  class BaseConfig(MashBaseConfig):
    serialization_strategy = {
        enum.Enum: EnumSerializer(),
    }
  

To yaml would yield:

field_one: my.module.MyEnum.A

instead of the default:

field_one: 1

[kdkavanagh]

I've realized this isnt specific to enums and is instead a product of Mashumaro only looking for direct matches when scanning for SerializationStrategies for a specific type, instead of considering a type's inheritance structure thru the MRO. I think this functionality could be added by recursing thru the provide type's __mro__[1:] inside https://github.com/Fatal1ty/mashumaro/blob/master/mashumaro/core/meta/code/builder.py#L1212C9-L1212C40

I believe the downstream code will still use the first match discovered, which if using the MRO, would be the child-most class, which is functionally desirable, falling back to strategies for parent classes only if ones for the children are not found.

Since this is a bigger change than specifically enums, affecting the way that any/all serialization strategies are resolved, I'm curious to get your thoughts @Fatal1ty. Perhaps it could become a setting on the strategy itself to optionally match child classes as well?

[Fatal1ty]

Perhaps it could become a setting on the strategy itself to optionally match child classes as well?

I like your idea if it will be implemented this way! We already have use_annotations parameter in SerializationStrategy, so the list of parameters can be extended with a new one.

@kdkavanagh do you wanna try to implement the idea?