[BUG]: drizzle-kit generate for unique index produces incorrect migration

[dmmulroy]

What version of drizzle-orm are you using?

0.31.1

What version of drizzle-kit are you using?

0.22.2

Describe the Bug

export const credential = pgTable(
    'credential',
    {
        id: serial('id').primaryKey(),
        userId: integer('user_id')
            .notNull()
            .references(() => user.id),
        active: boolean('active').notNull(),
        hash: text('hash').notNull(),
        createdAt: timestamp('created_at', { withTimezone: true, mode: 'date' }).defaultNow(),
        updatedAt: timestamp('updated_at', { withTimezone: true, mode: 'date' })
            .defaultNow()
            .$onUpdate(() => new Date())
    },
    (table) => {
                // Add this constraint as a migration
        return {
            activeIdx: uniqueIndex('active_credential_idx')
                .on(table.userId, table.active)
                .where(eq(table.active, true))
        };
    }
);

This produces the following migration as a prepared statement using $1

DROP INDEX IF EXISTS "active_credential_idx";--> statement-breakpoint
CREATE UNIQUE INDEX IF NOT EXISTS "active_credential_idx" ON "credential" USING btree (user_id,active) WHERE "credential"."active" = $1;

Expected behavior

It should produce a migration file like this:

DROP INDEX IF EXISTS "active_credential_idx";--> statement-breakpoint
CREATE UNIQUE INDEX IF NOT EXISTS "active_credential_idx" ON "credential" USING btree (user_id,active) WHERE "credential"."active" = true;

Environment & setup

No response

[dmmulroy]

Looks like it happens for more than just boolean columns per #2508