What is the best practice for altering migrations made prior to the fix for enums being created in a specific schema? I.E. in our first migration we created the base image to start with which had something like

CREATE TYPE "public"."TestType" AS ENUM ('FOO', 'BAR', 'BAZ');

We manually altered these files to take out the schema so our automated tests could run correctly

CREATE TYPE "TestType" AS ENUM ('FOO', 'BAR', 'BAZ');

But altering the migration manually results in a warning in prisma and probably isn't the best thing to do for our production systems I would think?

Hi Adam! It's pretty manual, but since that change is safe, it's fine to ignore the warning on deploy. I think we might want to remove these at some point.

Thanks!