Repository navigation
test: cover RFC length limits for domain() and hostname() - #493
Merged
Merged
Conversation
This was referenced Oct 10, 2026
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
1 participant
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.
#461 added the 253-character limit without tests. This adds regression coverage for the limits and label rules from RFC 1035 and RFC 1123: total length 253 accepted / 254 rejected, label length 63 accepted / 64 rejected, digit-leading labels accepted, leading or trailing hyphens and underscores rejected, plus the exact string from #413.
Tests only, no behaviour change. Verified that 8 of the new cases fail against the pre-#461
domain.pyand all pass on master.🤖 Generated with Claude Code