Zod z.stringbool is converted to string in the spec

[PseudoResonance]

input: z.object({
    override: z
        .boolean()
        .default(false)
        .optional(),
    }),

With the input shown, the spec says this is a boolean as expected, however Zod can't parse the input because it's a query string, and Zod expects a boolean, not a string.
.coerce.boolean() can be used instead, which theoretically should coerce the string to a boolean, but unfortunately that will convert "false" to true...
From my understanding, the way to overcome this is to use z.stringbool(), but now since it's technically a string, the spec defines the type as a string.

Is there a way to get around this and still define the type as a boolean in the spec, while still being able to parse the value?

[RobinTail]

it's a query string

It is the answer to your question, @PseudoResonance

When parsing GET request, the query is a string, all its parameters are strings.
So there must be some interpretation implemented that could treat some of those strings as "truthy" or "falsy" in order to get booleans out of them.

You can't have z.boolean() in input schema for GET request directly — it won't pass the validation, because the typeof is still string. You can have a string-based schema, having a transformer to boolean. z.stringbool() is a flexibly configurable shorthand for that purpose.

If you want booleans, use a request that supports body, for instance — POST.
The body os JSON encoded, so that its parser revives booleans before validation.

[PseudoResonance]

Yes, it does work this way, but it is confusing in the specs. For example, rendered in Scalar, it says "override Type: string default: false", and the query test UI will also have a string input instead of a boolean dropdown.

Technically the passed value will always be a string in GET, but I think it would make far more sense, and still be correct, to list a "stringbool" as simply a boolean in this case. Of course, providing a description can help clarify, but it's still not immediately clear that the expected value is a boolean.

[RobinTail]

@PseudoResonance , consider z.literal(["true", "false"]) if you want a third-party UI to have options for a dropdown.

[PseudoResonance]

If there aren't other options, then .literal(["true", "false"]).transform((val) => val === "true") is probably the best choice, but still feels wrong to me.

Regardless, thank you for taking your time to help!