[WIP] feat: prisma enum from JS enum

[Daidalos117]

This is proposed functionality for importing TS/JS enums into the schemix/prisma. We can do this manually now, but it would be nice if the library could support this way out of the box.
IMHO it should be preferred way to import JS enums, because it has numerous advantages.

• using enum anywhere / using already typed enums
• using default value for column from enum

Maybe better safety could be implemented because of this, not really sure for now. What do you think?

[ridafkih]

I like this! Will have a closer look once I land, currently on flight. c:

[ridafkih]

@Daidalos117 What do you think of the changes I've made? First, I ran the linter quickly and created some tests.

The real changes were that now you can pass in raw enum from TypeScript, and then if you are to assign each of those values a string it would reflect as a map on the enum in Prisma. Otherwise it would just default to the standard input.

  it("Should allow importing JS/TS enums through `fromJSEnum`", async () => {
    enum AvengersEnum {
      THOR,
      IRON_MAN,
      CAPTAIN_AMERICA,
      BLACK_WIDOW,
      HULK,
    }

    const avengersEnum = new PrismaEnum("Avengers").fromJSEnum(AvengersEnum);
    const asString = await avengersEnum.toString();
    expect(asString).toMatchSnapshot();
  });

This test produces the following output.

enum Avengers {
  THOR
  IRON_MAN
  CAPTAIN_AMERICA
  BLACK_WIDOW
  HULK
}

while the following produces what follows.

  it("Should allow mapping values through `fromJSEnum`", async () => {
    enum AvengersNameAcronymEnum {
      THOR = "TO",
      IRON_MAN = "TS",
      CAPTAIN_AMERICA = "SR",
      BLACK_WIDOW = "NR",
      HULK = "BB",
    }

    const avengersNameAcronymEnum = new PrismaEnum("Avengers").fromJSEnum(
      AvengersNameAcronymEnum
    );

    const asString = await avengersNameAcronymEnum.toString();
    expect(asString).toMatchSnapshot();
  });

enum Avengers {
  THOR             @map("TO")
  IRON_MAN         @map("TS")
  CAPTAIN_AMERICA  @map("SR")
  BLACK_WIDOW      @map("NR")
  HULK             @map("BB")
}

Let me know if you're okay with these changes, and if you see foresee any issues.

[Daidalos117]

@ridafkih looks very good to me! Good idea with the mapping, I didn't think of that :)

[ridafkih]

@Daidalos117 Awesome, this shouldn't affect any other implementations so it should be good to go! Think we're ready to get this in?

[ridafkih]

Actually, going to write some quick tests for setting default values.

[ridafkih]

Current status, looking into making enums on Schemix type-safe.

[dstoyanoff]

@ridafkih, this sounds like something I would love to have. Which part is not currently type-safe?