docs: clarify safeParse callback errors#127
Merged
Merged
Conversation
|
To preview the documentation for this pull request, visit the following URL:
|
leoafarias
marked this pull request as ready for review
July 15, 2026 11:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
safeParseErrorrethrow guarantee to constraint and refinement callbackssafeParseAsmappers returnSchemaTransformErrorfailures for thrown values, includingErrorvaluesllms.txtguidance alignedWhy
PR #126 corrected the old “never throws” wording, but the replacement made the
Errorrethrow guarantee appear universal. The runtime intentionally wraps transform and mapper callback failures, so the documentation needs to distinguish those callback categories.This is documentation-only and does not change runtime behavior.
Validation
npx --yes @docs.page/cli checkgit diff --check origin/main...HEAD