-
Notifications
You must be signed in to change notification settings - Fork 310
compose: Enforce max topic/content length by code points, following API #1239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
gnprice
merged 7 commits into
zulip:main
from
chrisbobbe:pr-topic-content-length-code-points
Jan 23, 2025
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
bf7576e
compose [nfc]: Add a TODO(#1238)
chrisbobbe 6b5966c
compose [nfc]: Comment on max-topic-length check about cutting off short
chrisbobbe be04a68
compose test [nfc]: Give enterTopic a dartdoc
chrisbobbe cb1eb7d
compose_box test [nfc]: Make a enterContent helper
chrisbobbe c0b9a5d
test [nfc]: Factor out `checkNoErrorDialog` helper
chrisbobbe e67b014
compose test: Test topic- and content-max-length validation errors
chrisbobbe a23309a
compose: Enforce max topic/content length by code points, following API
chrisbobbe File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fact about
.characters
isn't really used here, right? This could be any single emoji code point (for any of the emoji of the past decade or so, in the range U+10000 and up) and it'd have more UTF-16 code units than code points.I guess it is helpful that the tests below confirm that at M+1 code points we start rejecting the value even when it's less than M "characters" / grapheme clusters. So maybe the thing to do is to just add that to this function's doc: the number of characters in that sense is less than [n].