Currently, we have this:

GlobalTypeMapper.MapEnum<SomeEnum>("some_schema.some_enum");

Which contributes to the issues in the EF Core provider involving default schemas and detecting when to escape user defined type names.

npgsql/efcore.pg#605 attempts to address this from the provider-side, but it would be better if the type mapping treated names and schema's separately:

GlobalTypeMapper.MapEnum<SomeEnum>(name: "some_enum", schema: "some_schema");