Repository navigation
pack: the case warning says only what happens to names that differ in case - #103
Merged
enesismail merged 1 commit intoOct 5, 2026
Conversation
… case The warning for two names that differ only in capitalisation said they would collide once the site was served, and that the site would serve whichever of them the platform kept. Neither is true. Every step that stores and serves a site keeps a path's letter case, so each spelling is its own file at its own address, and an address with the wrong case is a page that is not there. The detector is unchanged: it still finds every such group over the whole walked tree. Because that tree includes files that never reach the site, the text now says what happens if the names are published rather than that they will be, and what to do about it: keep one if they are meant to be one file, otherwise rename one. A row pins both strings for a two-name and a three-name group and refuses any return of the two false claims.
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.
What was wrong. The warning for names that differ only in capitalisation said they "would collide once the site is served" and that the site "will serve whichever the platform kept". Neither is true. Every step that stores and serves a site keeps a path's letter case: each spelling is its own file at its own address, and an address with the wrong case is a page that is not there. That was checked on a live site: the real address answered, and the same address with one letter's case changed did not.
What changes.
Row (written first, and red against the old text on every assertion): the exact message and next step for a two-name and a three-name group, read from the function's own output, plus a refusal of "collid" and "whichever the platform kept" in either field, case-folded.
Mutations, each run and reverted: the old message restored; the old next step restored; the count's two words swapped; "capitalisation" spelled with a z; "or they collide" appended; the message's trailing colon removed. Each reds both subtests.