exclusive-coral

Zod v4 parse path params always string?

reacttypescript

I'm using

@tanstack/zod-adapter

@tanstack/zod-adapter

for parsing path params:

export const Route = createFileRoute(
  "/route/$one/$two/$three",
)({
  params: zodValidator(
    z.object({
      one: z.number(),
      two: z.string(),
      three: z.string(),
    }),
  )},
  component: RouteComponent,
});

export const Route = createFileRoute(
  "/route/$one/$two/$three",
)({
  params: zodValidator(
    z.object({
      one: z.number(),
      two: z.string(),
      three: z.string(),
    }),
  )},
  component: RouteComponent,
});

However, when routing using a

<Link />

<Link />

component:

<Link
  to="/route/$one/$two/$three"
  params={{
    one: 1234,
    two: "value",
    three: "otherValue",
  }}
>
  {/* ... */}
</Link>

<Link
  to="/route/$one/$two/$three"
  params={{
    one: 1234,
    two: "value",
    three: "otherValue",
  }}
>
  {/* ... */}
</Link>

The expected result here would be that it was a number inside the route, instead Zod throws an error since the param is a string???

TanStack•2w ago

exclusive-coral

Zod v4 parse path params always string?

reacttypescript

I'm using

@tanstack/zod-adapter

@tanstack/zod-adapter

for parsing path params:

export const Route = createFileRoute(
  "/route/$one/$two/$three",
)({
  params: zodValidator(
    z.object({
      one: z.number(),
      two: z.string(),
      three: z.string(),
    }),
  )},
  component: RouteComponent,
});

export const Route = createFileRoute(
  "/route/$one/$two/$three",
)({
  params: zodValidator(
    z.object({
      one: z.number(),
      two: z.string(),
      three: z.string(),
    }),
  )},
  component: RouteComponent,
});

However, when routing using a

<Link />

<Link />

component:

<Link
  to="/route/$one/$two/$three"
  params={{
    one: 1234,
    two: "value",
    three: "otherValue",
  }}
>
  {/* ... */}
</Link>

<Link
  to="/route/$one/$two/$three"
  params={{
    one: 1234,
    two: "value",
    three: "otherValue",
  }}
>
  {/* ... */}
</Link>

The expected result here would be that it was a number inside the route, instead Zod throws an error since the param is a string???

Zod v4 parse path params always string?

Similar Threads

Zod v4 parse path params always string?

Similar Threads

Similar Threads

Similar Threads