feat(messaging): add 2000-char limit warning to chat input#331
Merged
Conversation
CareConnect Quality Gate Report
CareConnect — Security & Quality Analysis ReportReport Header
All timestamps are reported in Coordinated Universal Time (UTC). Pull Request
Commit Details
Legend
Tool Results Summary
Full artifact bundle available in the workflow run artifacts. |
cbmahoney
approved these changes
Mar 29, 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
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.
o Enforced a hard limit of 2000 characters on chat input.
o Added a live character count indicator when users approach the limit (starting at 1800).
o Applied warning colors as the user nears/reaches the limit:
o neutral near threshold
o warning close to limit
o error at the limit
o Disabled the send action when input is invalid (over limit / blocked).
o Added a guard in send logic so over-limit text cannot be sent even if triggered programmatically.
This prevents oversized messages, gives clear user feedback before reaching the limit, and avoids failed/invalid message submissions.