is there a rationale behind this decision when handling serialization of a dagster Resource? https://github.com/dagster-io/dagster/blob/6149c01ff8e317775b39e480288b89d88fe0eeb[…]hon_modules/dagster/dagster/_config/pythonic_config/__init__.py This conflicts with the use_enum_value pydantic configuration: https://docs.pydantic.dev/latest/api/config/#pydantic.config.ConfigDict.use_enum_values

Hi Fabio, this decision was made to correspond with the way that enums were addressed in the old Dagster config types system (which used enum names).

thanks for the swift response @ben !