fix(v4): improve error messages for Infinity, NaN, and Invalid Date #5230
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
This PR fixes the confusing error messages when validating special numeric values (Infinity, NaN) and invalid dates with Zod schemas. Closes #5186
Problem
When parsing Infinity with z.number(), the error message was:
Invalid input: expected number, received number
This was confusing because it appeared to say the same type was both expected and received.
Solution
issue.received
field before falling back to parsedType()