Nested Schema Titles and Observability: How do I know which nested schema fails in a 300 field schema?

[MkEtlingerJH]

Hey Valibot team!

I am working on a product where our Python backend doesn't have strict typing which means on the frontend I need to do some stuff:

1. Set a v.title() on all ~50 of the schemas for this object
2. Using safeParse and when there's a validation error, I want to log the failing schema
3. The failing schema should include title of the nearest failing schema in the logs so that if it's 3 levels deep, the schema title would be the nearest failing one

Our problem is more of an architectural/data issue so I think the right answer is: "stop having a crazy nested schema, and separate/flatten your data domains" but alas, that will take some time to do.

Is it possible to include getTitle() inside of result.issues?

I was looking here: https://github.com/open-circle/valibot/blob/main/library/src/utils/_addIssue/_addIssue.ts but I only see references to (isSchema ? getSchemaMessage(issue.lang) : null) .

Thanks for any help!

[dosubot[bot]]

Hi @MkEtlingerJH! I'm Dosu and I'm helping the Open Circle team.

Short answer: No, title metadata is not currently included in result.issues, and there's no built-in way to get it there. The separation between schema metadata (like title()) and validation issues is an intentional architectural choice in Valibot [1].

Here's why: The BaseIssue interface contains fields like kind, type, input, expected, received, message, and path — but no title or reference back to the originating schema's metadata [2]. The _addIssue utility resolves error messages through a priority cascade but never accesses schema metadata like titles [3].

What you do get is the path property on each issue — an array of path items that shows the exact structural location of the failure (e.g., object keys, array indices). You can use getDotPath() to convert this to a readable string like "user.address.zip" [4].

Possible workaround: You could build a utility that, given an issue's path, traverses your schema tree and calls getTitle() [5] on each nested schema along the way to find the nearest titled ancestor. Something like:

import { getTitle, getDotPath } from 'valibot';

function getNearestTitle(schema, issue) {
  // Walk your schema structure using issue.path segments
  // Call getTitle() on each level to find the nearest titled schema
  // Return the first title found walking from deepest to shallowest
}

This isn't automated today, so you'd need to maintain the traversal logic yourself.

Alternatively, you could set custom message functions on your schemas that include the title context in the error message directly, which would then appear in issue.message.

Your intuition about this being a potential feature request (getTitle() inside issues) seems reasonable — it would be a change to the _addIssue utility to optionally capture the title metadata from the schema context when creating issues.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[fabian-hiller]

@MkEtlingerJH did this answer your question? The issue.path is how you can figure out the origin of the issue within the schema.

[MkEtlingerJH]

Yep this makes sense!

I think the path is sufficient. I think I just wanted to see something like:

× Invalid type: Expected ("thing" | "otherThing") but received "notValidThing" → at MySchemaTItle: the_path.to_the.0.exact_field.input

That would allow someone to simply copy/paste the exact schema title but it's only a minor annoyance following the path top to bottom.

Thanks for the reply!