fix(v4): reflect inclusive boundaries in minLength/maxLength issue objects #4591
Conversation
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
|
Good catch, thanks! |
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.
This updates the
minLengthandmaxLengtherrors in v4 to include theinclusiveproperty. Currently, I believe validations likez.string().max()use inclusive boundaries (zod/packages/zod/src/v4/core/checks.ts
Line 619 in 50e9afb
In v3, validations like
z.string().max()also used inclusive boundaries, and the issue objects correctly indicated this.If this change was intentional as part of the migration to v4, or if I have misunderstood the current behavior, please feel free to close this pull request!