Type-checking methods do not accept `unknown`

As of version 1.2.5, the parse, is and check methods on ZodType expect to receive an argument which is already of the schema’s type. This is surprising to me; at version 1.0.15 I was passing unknown values to these functions, since the input is of unknown type (typically from IO) and the functions are being called explicity to discover whether the value matches the type.

Since I don’t want to incorrectly-type the values before they are checked, it seems the only option here is to use any, which from my point of view is strictly worse than unknown.

Is there a downside I’m not seeing to permitting unknown as input to these functions?

[hen-x]

@vriad I think it would be a good compromise to have the methods accept T | unknown. That way we can reject any obviously-incorrect values (ie those for which we already have an incompatible type), while allowing users to supply unknown values without resorting to as any.

(For context, I am working in an environment which makes it a lint-violation to use the type any, since unknown is a safer alternative.)

[colinhacks]

@hen-zone @nicoespeon Released in zod@1.2.6