docs: fix z.custom example and reference z.templateLiteral #5606
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

What changed
This PR improves the
z.custom()documentation by adding a clearer, more representativeexample that demonstrates its intended use with unsupported or external types, such as
class instances.
A note was also added to clarify that
z.templateLiteral()should be preferred whenworking with template string literal schemas.
Why
The previous documentation could be confusing, as it referenced template string literals
without clearly distinguishing when
z.custom()is appropriate versus when a dedicatedschema like
z.templateLiteral()should be used.This change improves clarity without removing or altering any existing API functionality.
Scope
Related issue
Closes #5605