Skip to content

fix(ui): fix keystroke reporting#2545

Merged
Brazol merged 4 commits intofeat/design-refreshfrom
fix/refreash-indicator
Mar 17, 2026
Merged

fix(ui): fix keystroke reporting#2545
Brazol merged 4 commits intofeat/design-refreshfrom
fix/refreash-indicator

Conversation

@Brazol
Copy link
Contributor

@Brazol Brazol commented Mar 17, 2026

Submit a pull request

Linear: FLU-425

Github Issue: #

CLA

  • I have signed the Stream CLA (required).
  • The code changes follow best practices
  • Code changes are tested (add some information if not applicable)

Description of the pull request

Screenshots / Videos

Before After
img img

Summary by CodeRabbit

  • Improvements
    • Refined message input event handling for improved typing indicator responsiveness and UI state management in the chat interface.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 17, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0e3bf338-b8a3-4c54-98d0-a93215660ede

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • ✅ Review completed - (🔄 Check again to review again)
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/refreash-indicator
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

CodeRabbit can generate a title for your PR based on the changes with custom instructions.

Set the reviews.auto_title_instructions setting to generate a title for your PR based on the changes in the PR with custom instructions.

@codecov
Copy link

codecov bot commented Mar 17, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.78%. Comparing base (f3a9780) to head (e5ed929).
⚠️ Report is 2 commits behind head on feat/design-refresh.

Additional details and impacted files
@@                   Coverage Diff                   @@
##           feat/design-refresh    #2545      +/-   ##
=======================================================
+ Coverage                64.77%   64.78%   +0.01%     
=======================================================
  Files                      437      437              
  Lines                    26536    26546      +10     
=======================================================
+ Hits                     17189    17199      +10     
  Misses                    9347     9347              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (2)
packages/stream_chat_flutter/test/src/message_input/message_input_test.dart (2)

446-447: Comment/duration mismatch.

The comment states "350ms" but the pump duration is 1 second. Consider updating the comment to accurately reflect the actual duration or adjust the duration to match.

-        // Pump past the debounce/throttle timers (350ms)
-        await tester.pump(const Duration(seconds: 1));
+        // Pump past the debounce/throttle timers
+        await tester.pump(const Duration(milliseconds: 350));

Alternatively, if 1 second is intentional for other reasons (e.g., accounting for async operations), update the comment accordingly.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@packages/stream_chat_flutter/test/src/message_input/message_input_test.dart`
around lines 446 - 447, The inline comment above the tester.pump call is
inconsistent: it says "350ms" but the code calls await tester.pump(const
Duration(seconds: 1)); — update the comment to match the actual Duration (e.g.,
change to "1s" or "1000ms") or change the Duration to 350 milliseconds if that
was the intended debounce/throttle wait; ensure you modify the comment next to
the tester.pump(...) invocation so the comment and Duration remain consistent.

488-489: Same comment/duration mismatch as above.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@packages/stream_chat_flutter/test/src/message_input/message_input_test.dart`
around lines 488 - 489, The comment says "Pump past the debounce/throttle timers
(350ms)" but the test uses await tester.pump(const Duration(seconds: 1)),
causing a comment/duration mismatch; update either the comment or the Duration
in the test in message_input_test.dart (the test around the "Pump past the
debounce/throttle timers" line) so they match — replace Duration(seconds: 1)
with Duration(milliseconds: 350) if you intend to wait 350ms, or change the
comment to reflect 1 second if that was intentional.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@packages/stream_chat_flutter/test/src/message_input/message_input_test.dart`:
- Around line 446-447: The inline comment above the tester.pump call is
inconsistent: it says "350ms" but the code calls await tester.pump(const
Duration(seconds: 1)); — update the comment to match the actual Duration (e.g.,
change to "1s" or "1000ms") or change the Duration to 350 milliseconds if that
was the intended debounce/throttle wait; ensure you modify the comment next to
the tester.pump(...) invocation so the comment and Duration remain consistent.
- Around line 488-489: The comment says "Pump past the debounce/throttle timers
(350ms)" but the test uses await tester.pump(const Duration(seconds: 1)),
causing a comment/duration mismatch; update either the comment or the Duration
in the test in message_input_test.dart (the test around the "Pump past the
debounce/throttle timers" line) so they match — replace Duration(seconds: 1)
with Duration(milliseconds: 350) if you intend to wait 350ms, or change the
comment to reflect 1 second if that was intentional.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 45ca077f-5c7f-4e7c-982b-3df8088f48a9

📥 Commits

Reviewing files that changed from the base of the PR and between f3a9780 and e5ed929.

📒 Files selected for processing (2)
  • packages/stream_chat_flutter/lib/src/message_input/stream_message_input.dart
  • packages/stream_chat_flutter/test/src/message_input/message_input_test.dart

@Brazol Brazol merged commit ec41292 into feat/design-refresh Mar 17, 2026
9 checks passed
@Brazol Brazol deleted the fix/refreash-indicator branch March 17, 2026 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants