Type changes in 3.23 breaks some code about zod HOT 2 CLOSED

Sorry for the inconvenience with this. The short answer is that this has been solved in 3.23.2 by setting the default Output and Input back to any from unknown (as in 3.23.0). This behavior is more intuitive in more cases.

Were that not the case, the real solution here would be to extract both HelloOutput and HelloInput like so (if I'm understanding correctly). That is:

type Branded<T, Brand> = T & { __brand: Brand };
type BrandedString = Branded<string, "BrandedString">;
const aBrandedString = z.string() as unknown as z.ZodSchema<BrandedString>;

const helloSchema = z.object({
  name: aBrandedString,
});
type HelloOutput = z.output<typeof helloSchema>;
type HelloInput = z.input<typeof helloSchema>;

// eslint-disable-next-line @typescript-eslint/no-explicit-any
const func = (hello: z.ZodObject<any, any, any, HelloOutput, HelloInput>) => {
  // ...
};

const funcResult = func(helloSchema); // this type works now

from zod.

I can see you closed the issue.
Just jotting down for history.

I had tested 3.23, but that didn't do it.
However, the new 3.24 did. (I can see that it reverted back to Input = Output).

The real solution provided in code I don't think would help us because in our real code the func is a generic (I mentioned it briefly but not in the simplified example code). All we know at the time of writing is the generic type, we don't know the schema. So if I'm not forgetting anything obvious (bit tired after a busy week) in our case, the solution wouldn't be the desired route we would like to take, would mean adding a lot of code.

Anyway, thank you for your response!
And since the reversion in 3.24 it's all working again.

from zod.