Repository navigation
feat: add NonZero types to range validation - #405
Open
svix-jbrown wants to merge 1 commit into
Open
svix-jbrown wants to merge 1 commit into
svix-jbrown wants to merge 1 commit into
Conversation
svix-jbrown
force-pushed
the
feat/add-nonzero
branch
from
October 19, 2026 18:10
0105bde to
99159e3
Compare
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.
This adds support for using
validate_rangewith NonZero types. You can use either NonZero or regular types as the bounds.Fixes #269. Supersedes #270