Repository navigation
docs: preserve CIDR tuple types in subnetMatch example - #215
Merged
whitequark merged 1 commit intoSep 27, 2026
Merged
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
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.
Use parseCIDR() in the named-range README example so its inferred types work in both JavaScript and TypeScript. Add a short explanation of why separately declared array literals lose tuple inference.
This applies the solution already suggested by @Manouchehri in #170 to the current documentation; no runtime or declaration changes.
Validation:
I encountered this while using ipaddr.js in a TypeScript webhook inspection tool. This documentation patch was prepared with AI assistance and checked with the commands above.