[BUG]: drizzle-zod doesn't parse mysqlEnum as z.ZodEnum

[ryuudotgg]

Report hasn't been filed before.

• I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?

0.38.0

What version of drizzle-kit are you using?

0.30.0

Other packages

[email protected]

Describe the Bug

export const table = mysqlTable(
  "table",
  { enum: mysqlEnum("enum", ["One", "Two"]).notNull() },
);

export const schema = createInsertSchema(table);

The enum here should return a z.ZodEnum instead of a z.ZodString.

It looks like just a TypeScript issue, it's done during runtime: column.ts#L57

It used to work in [email protected]

[L-Mario564]

May I know the content of your tsconfig.json file? mysqlEnum returns z.ZodEnum in Drizzle's test suite, and I'm unable to reproduce this at the moment.

[ryuudotgg]

@L-Mario564, I rolled back to 0.5.1 for now, here's my tsconfig:

{
  "$schema": "https://json.schemastore.org/tsconfig",
  "extends": "./base.json",
  "compilerOptions": {
    "declaration": true,
    "declarationMap": true,
    "emitDeclarationOnly": true,
    "noEmit": false,
    "outDir": "${configDir}/dist"
  }
}

{
  "$schema": "https://json.schemastore.org/tsconfig",
  "compilerOptions": {
    "esModuleInterop": true,
    "skipLibCheck": true,
    "target": "ESNext",
    "lib": ["ESNext"],
    "allowJs": true,
    "resolveJsonModule": true,
    "moduleDetection": "force",
    "isolatedModules": true,

    "incremental": true,
    "disableSourceOfProjectReferenceRedirect": true,
    "tsBuildInfoFile": "${configDir}/.cache/tsbuildinfo.json",

    "strict": true,
    "noUncheckedIndexedAccess": true,
    "checkJs": true,

    "module": "Preserve",
    "moduleResolution": "Bundler",
    "noEmit": true
  },
  "exclude": ["node_modules", "build", "dist", ".next"]
}

[pedrocarlo]

The same happens to me with pgEnum and text({enum:}) and varchar({enum:}). Drizzle zod translates it as an array of strings

[L-Mario564]

@nemanjastanic Is the sample code you provided is all that is required to reproduce the bug? I'm still completely unable to reproduce this.

[ryuudotgg]

Hey @L-Mario564, I just retried this, it seems it's caused by #3732. I missed this previously because I managed to suppress the error by adding .partial({}).

Please feel free to close this issue if you want to consider it a duplicate!

[L-Mario564]

@nemanjastanic Will close this in favor of the one you mentioned. Thanks.