Path Key not Available in safeParse

[jdgamble555]

I'm trying to create an error message, but there doesn't seem to be any way to tell which key or input the problem is coming from, since the path variable is null. Here is the issue. I am passing an empty input object.

I need to tell the user which input is the problem... ?

{
  kind: 'schema',
  type: 'string',
  input: undefined,
  expected: 'string',
  received: 'undefined',
  message: 'Invalid type: Expected string but received undefined',
  requirement: undefined,
  path: undefined,
  issues: undefined,
  lang: undefined,
  abortEarly: true,
  abortPipeEarly: undefined
}

with this simple schema:

export const courseSchema = object({
    name: string(),
    description: string(),
    visibility: string()
});

Thanks,

J

[fabian-hiller]

Can you reproduce the problem in our playground?

[jdgamble555]

Can ignore this. I wasn't using decode or Object.fromEntries() from my form data.

Thanks,

J

[jdgamble555]

Actually yes, it still doesn't work when you try and change the message:

Playground

J

[fabian-hiller]

Each schema is independent and therefore has no information about its parent. Because the parent lazily adds the path to the issue, it is not available when the child's message is calculated.

[jdgamble555]

Hey Fabian, you don't think it is important to be able to calculate a new message with the actual name of the input that has the problem? Granted, yes, this can be done locally instead of globally. Just a thought.

[fabian-hiller]

I agree that this functionality would add value to the library, but it would force us to compute the message at the very end when calling parse or safeParse.