fix: reject oversized rich-text edits without truncation - #192
Merged
Merged
Conversation
dazzatronus
force-pushed
the
fix/clamp-rich-text-max-length
branch
from
September 25, 2026 01:50
bc0e894 to
86806f0
Compare
dazzatronus
changed the title
github-actions Bot
pushed a commit
that referenced
this pull request
Sep 25, 2026
## [2.22.6](v2.22.5...v2.22.6) (2026-09-25) ### Bug Fixes * reject oversized rich-text edits without truncation ([#192](#192)) ([21dcdf1](21dcdf1))
|
🎉 This PR is included in version 2.22.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Oversized text must not crash editing or be silently cut through a Unicode character or variable token. Reject edits and variable insertions when either the template or resolved text exceeds 5,000 characters, using the textarea's native validation message. Preserve the draft and saved bindings so the user can correct the input.
Cancel pending saves on variable insertion and keep the popup open when validation fails. Regression tests stay in the public SDK suite.
Verify:
npm run verify:cipasses on Node 22, including 2,088 tests. Four integration cases cover Unicode boundaries, template and resolved-value limits, and binding preservation.