Add enumType option that matches Prisma client's enum definitions

[arithmetric]

As described in #5, this generator's output for enums does not match the enums defined in the Prisma client. This can cause TypeScript errors due to mismatching types.

This PR adds a new object value to the "enumType" option that generates const and type definitions for enums to match Prisma Client.

For example, if an enum is defined in Prisma’s schema file like this:

enum UserStatus {
  ACTIVE
  BLOCKED
  PENDING
}

In the Prisma client (index.d.ts), the enum is defined as:

export namespace $Enums {
  export const UserStatus: {
  ACTIVE: 'ACTIVE',
  BLOCKED: 'BLOCKED',
  PENDING: 'PENDING'
};

export type UserStatus = (typeof UserStatus)[keyof typeof UserStatus]

With the enumType option value "object", this generator produces the following output:

export const UserStatus = {
  ACTIVE: "ACTIVE",
  BLOCKED: "BLOCKED",
  PENDING: "PENDING"
};

export type UserStatus = (typeof UserStatus)[keyof typeof UserStatus];

[mogzol]

As mentioned in my comment on your issue, the exported type should be identical to the exported type when using stringUnion. Still, the new object type you've added is nice because it lets you use the const export like an enum to access the values, while avoiding the compatibility issues caused by using typescript enums. And since the type is identical to the stringUnion types, it could even be made the default without breaking backwards compatibility.

I will try to merge this and create a new release later today.

[mogzol]

Just realized that the types exported will always just be "string" due to type widening. I just pushed a change to add as const, so that the types will be the proper union. See 704b819

[mogzol]

This is now published as v1.5.0. Thanks for the PR!