safeParse for searchParams

[cw-1988]

the getting/parsing of searchParams is a bit cumbersome: example
Adding a function that safeparses to the searchSchema would be nice.

[cw-1988]

found something with query-string
it makes sure that all params that can be parsed will be parsed (partial parse)

export function safeParseSearchParams<T extends z.AnyZodObject>(schema: T, request: NextRequest): Partial<z.infer<T>> {
  const params = queryString.parse(request.nextUrl.search, { parseBooleans: true })
  const shape = schema.shape;
  const parsed: Record<string, any> = {};

  for (const key in shape) {
    if (shape.hasOwnProperty(key)) {
      const fieldSchema: ZodTypeAny = shape[key];
      const result = fieldSchema.safeParse(params[key])
      if (result.success)
        parsed[key] = result.data;
    }
  }

  return parsed;
}

[jherr]

Nice! So this would be an included helper function that can be used for search params validation?

[cw-1988]

Oh yeah, just plug in the schema and the NextRequest. Then query-string parses the searchString into an object. Every field of that object then gets validated and potentially removed, so only valid searchParams make it. The kinda least destructive approach I thought...

I didn't check if zod throws errors on fields it doesn't cover, gotta check that. I think there could also be some error handling/logging to give feedback on which parse failed, but right now it serves its purpose^^

[jherr]

Once you've done that feel free to PR and I'll check it out as well. Thank you!

…

On Mon, Jun 17, 2024 at 2:24 PM Christoph Wolf ***@***.***> wrote: Oh yeah, just plug in the schema and the NextRequest. Then query-string parses the searchString into an object. Every property of that object then gets validated and removed from the object, so only valid searchParams make it. The kinda least destructive approach I thought... I didn't check if zod throws errors on fields it doesn't cover, gotta check that. I think there could also be some error handling/logging to give feedback on which parse failed, but right now it serves its purpose^^ — Reply to this email directly, view it on GitHub <#37 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFO6FT37VYI4CZJBTVHIDZH5H2NAVCNFSM6AAAAABJN3GOG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZUGQ2TCMJWGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[cw-1988]

damn i just realized you already use query-string... since you're only using stringify is there anything against fast-querystring?
https://www.npmjs.com/package/fast-querystring
And I created a version that doesn't use any querystring parser.

Also are there any rules you want to apply for booleans? what should be considered as true? "true" or just the mentioning of the key?
I also think it would be an antipattern to use nested values like array[foo][bar[baz] in a querystring. I'd rather want to enforce it to be part of a json body when the object is more complex than just a couple strings, bools and numbers.

PR is coming shortly ;-)

[cw-1988]

pff perfect now i see zod.coerce^^ goddammit...

alright looks like i will take some more time for an updated version ;-)