Repository navigation
Conversation
|
@sean0407 is attempting to deploy a commit to the naman's projects Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
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.
Summary
textLayout wrap at whitespace boundaries + split oversized tokens at grapheme boundaries when a fixed width is setFixes #25.
Evidence
main, both new regression cases fail: an unbroken URL stays on one line, and the resulting grapheme text exceeds the fixed layout width.npm testpasses (150 Vitest tests and 3 sync relay tests);npm run typecheckpasses;npm run buildcompletes.Merge Danger
Door: Two-way
The change only affects measured wrapping when a fixed width is set; autosized text keeps its existing path.
Blast Radius: Contained