Conversation
renefloor
changed the title
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThis PR refactors the message composition architecture by splitting responsibilities between ChangesMessage Composer Redesign
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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. Comment |
renefloor
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
packages/stream_chat_flutter/lib/src/components/message_composer/message_composer_component_props.dart (1)
10-18:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winRemove the stale
messageparameter docs.The constructor comment still documents
[message], butMessageComposerComponentPropsno longer exposes that field. That leaves the generated API docs pointing to a nonexistent argument.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/stream_chat_flutter/lib/src/components/message_composer/message_composer_component_props.dart` around lines 10 - 18, The constructor doc for MessageComposerComponentProps still references a nonexistent [message] parameter; edit the doc comment above the const MessageComposerComponentProps(...) to remove the stale `/// [message] is the message for the message composer component.` line (or any other mention of `message`) so the generated API docs no longer point to a non-existent argument.
🧹 Nitpick comments (4)
packages/stream_chat_flutter/lib/src/components/message_composer/stream_chat_message_input.dart (1)
279-289: 💤 Low valueInverted early-return is confusing in
onLongPressCancel.The check
if (audioRecorderController.isRecording) return;plus the comment "Return if the recording is already started" implies the cancel path is only meaningful when recording has not started — which matches Flutter'sonLongPressCancelsemantics (fires before recognition). However, the parallelonLongPressStartuses the same exact guard with the same comment to prevent double-start. Consider tightening the comment to clarify that we want the "hold to record" hint to be shown only when the user released before recording began.- onLongPressCancel: () async { - // Return if the recording is already started. - if (audioRecorderController.isRecording) return; + onLongPressCancel: () async { + // Skip if recording has already started; cancel only handles + // the case where the long-press never reached recognition. + if (audioRecorderController.isRecording) return;🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/stream_chat_flutter/lib/src/components/message_composer/stream_chat_message_input.dart` around lines 279 - 289, Clarify the inverted early-return in onLongPressCancel: the guard currently reads "Return if the recording is already started" but this callback should show the "hold to record" hint only when recording has NOT started. Update the comment on the check in onLongPressCancel (and make it symmetric with onLongPressStart) to state that if audioRecorderController.isRecording is true we should bail because a recording is already in progress, otherwise call widget.feedback.onRecordStartCancel(context) and audioRecorderController.showInfo(context.translations.holdToRecordLabel) to inform the user they released before recording began; reference onLongPressCancel, audioRecorderController.isRecording, widget.feedback.onRecordStartCancel, audioRecorderController.showInfo and context.translations.holdToRecordLabel when locating the change.packages/stream_chat_flutter/lib/src/message_input/stream_message_composer.dart (1)
61-99: ⚖️ Poor tradeoffConsider exposing a
MessageComposerPropsconstructor alongside the named parameters.The 35+ parameters are now duplicated three times across
StreamMessageComposer,MessageComposerProps, and the parameter forwarding block. AStreamMessageComposer.fromProps({required MessageComposerProps props})named constructor (or making the public ctor take apropsobject) would let advanced callers and component-factory authors reuse aMessageComposerPropsinstance without re-listing every field, while keeping the convenience constructor for typical usage.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/stream_chat_flutter/lib/src/message_input/stream_message_composer.dart` around lines 61 - 99, The constructor duplicates 30+ parameters between StreamMessageComposer and MessageComposerProps; add a second constructor StreamMessageComposer.fromProps({required MessageComposerProps props, Key? key}) (or change the public ctor to accept an optional props parameter) and wire that constructor to set this.props directly so callers can pass a pre-built MessageComposerProps instead of re-specifying every field; keep the existing named-parameter convenience ctor but refactor it to build MessageComposerProps(...) and forward to the new fromProps initializer to avoid parameter duplication and ensure symbols StreamMessageComposer and MessageComposerProps are used consistently.packages/stream_chat_flutter/example/lib/tutorial_part_4.dart (1)
147-151: ⚡ Quick win
StreamMessageInputControllercreated inbuild()is never disposed — resource leak.
StreamMessageInputControlleris aValueNotifierthat requires an explicitdispose()call. Creating it inline inside aStatelessWidget.build()means a new instance leaks on every rebuild with no disposal path. As tutorial code, this also models the pattern incorrectly for developers.
StreamMessageInputControllerrequiresmessageInputController.dispose()to be called in the owning state'sdispose()method.Convert
ThreadPageto aStatefulWidgetto manage the controller lifecycle properly.🛡️ Proposed fix
-class ThreadPage extends StatelessWidget { - const ThreadPage({ +class ThreadPage extends StatefulWidget { + const ThreadPage({ super.key, this.parent, }); final Message? parent; `@override` - Widget build(BuildContext context) { + State<ThreadPage> createState() => _ThreadPageState(); +} + +class _ThreadPageState extends State<ThreadPage> { + late final StreamMessageInputController _messageInputController = + StreamMessageInputController(message: Message(parentId: widget.parent!.id)); + + `@override` + void dispose() { + _messageInputController.dispose(); + super.dispose(); + } + + `@override` + Widget build(BuildContext context) { return Scaffold( appBar: StreamThreadHeader( - parent: parent!, + parent: widget.parent!, ), body: Column( children: <Widget>[ Expanded( child: StreamMessageListView( - parentMessage: parent, + parentMessage: widget.parent, ), ), StreamMessageComposer( - messageInputController: StreamMessageInputController( - message: Message(parentId: parent!.id), - ), + messageInputController: _messageInputController, ), ], ), ); } }🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/stream_chat_flutter/example/lib/tutorial_part_4.dart` around lines 147 - 151, ThreadPage currently constructs StreamMessageInputController inline in build(), leaking a ValueNotifier on each rebuild; convert ThreadPage from a StatelessWidget to a StatefulWidget, move instantiation of StreamMessageInputController (with Message(parentId: parent!.id)) into the State class (initState) and store it as a field, pass that field into StreamMessageComposer via the messageInputController parameter, and override dispose() in the State to call messageInputController.dispose() to properly release resources.packages/stream_chat_flutter/example/lib/tutorial_part_6.dart (1)
177-181: ⚡ Quick winSame
StreamMessageInputControllerdisposal issue astutorial_part_4.dart.
ThreadPagehere is also aStatelessWidgetcreating aStreamMessageInputControllerinline inbuild(). Apply the sameStatefulWidgetrefactor described fortutorial_part_4.dart.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/stream_chat_flutter/example/lib/tutorial_part_6.dart` around lines 177 - 181, ThreadPage currently creates a StreamMessageInputController inline inside build() (via StreamMessageInputController(message: Message(parentId: parent!.id))) which leads to the same disposal/leak issue as in tutorial_part_4.dart; refactor ThreadPage from a StatelessWidget to a StatefulWidget, add a private StreamMessageInputController field (initialized in initState using Message(parentId: parent!.id) or using widget props), pass that controller into StreamMessageComposer, and override dispose() to call controller.dispose() so the controller is created once per widget instance and properly cleaned up.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@migrations/redesign/message_composer.md`:
- Line 87: The phrasing incorrectly states the removed parameters were in an
older StreamMessageComposer; update the sentence and any related headings to
state that the parameters previously belonged to StreamMessageInput (the
pre-migration type) and not StreamMessageComposer (the new name introduced by
this PR). Locate the sentence "Many parameters that existed in older versions of
`StreamMessageComposer` have been removed." and change it to reference
`StreamMessageInput`, and scan the surrounding paragraph/table captions to
ensure all mentions consistently say "StreamMessageInput" (or "previous
StreamMessageInput") as the source of the removed parameters.
In `@packages/stream_chat_flutter/lib/src/localization/translations.dart`:
- Around line 102-104: Fix the typo in the doc comment for the getter
alsoSendAsDirectMessageLabel by removing the stray extra double-quote so the
sentence reads correctly (e.g., change 'checkbox""' to 'checkbox'); update the
three-line comment above String get alsoSendAsDirectMessageLabel; to ensure
generated docs don't contain the unintended quote.
In
`@packages/stream_chat_flutter/lib/src/message_input/stream_message_composer.dart`:
- Around line 1015-1031: The addedAttachments lookup is using
pickerController.value.attachments but addedIds are IDs present in
_effectiveController.attachments (message controller) and absent from the
picker, so firstWhere will throw; change the mapping that builds
addedAttachments to search _effectiveController.attachments (or the effective
controller's attachments collection used elsewhere in this file) instead of
pickerController.value.attachments so you retrieve the actual attachments to add
before calling pickerController.addAttachment for each.
In `@packages/stream_chat_flutter/README.md`:
- Line 102: Update the broken README link for StreamMessageComposer: replace the
non-existent URL ending with /stream_message_composer/ with the correct Stream
docs path following the message_composer pattern (e.g.,
/message_composer/stream_message_input/), so the README's StreamMessageComposer
link points to the valid documentation page for
StreamMessageComposer/StreamMessageInput.
---
Outside diff comments:
In
`@packages/stream_chat_flutter/lib/src/components/message_composer/message_composer_component_props.dart`:
- Around line 10-18: The constructor doc for MessageComposerComponentProps still
references a nonexistent [message] parameter; edit the doc comment above the
const MessageComposerComponentProps(...) to remove the stale `/// [message] is
the message for the message composer component.` line (or any other mention of
`message`) so the generated API docs no longer point to a non-existent argument.
---
Nitpick comments:
In `@packages/stream_chat_flutter/example/lib/tutorial_part_4.dart`:
- Around line 147-151: ThreadPage currently constructs
StreamMessageInputController inline in build(), leaking a ValueNotifier on each
rebuild; convert ThreadPage from a StatelessWidget to a StatefulWidget, move
instantiation of StreamMessageInputController (with Message(parentId:
parent!.id)) into the State class (initState) and store it as a field, pass that
field into StreamMessageComposer via the messageInputController parameter, and
override dispose() in the State to call messageInputController.dispose() to
properly release resources.
In `@packages/stream_chat_flutter/example/lib/tutorial_part_6.dart`:
- Around line 177-181: ThreadPage currently creates a
StreamMessageInputController inline inside build() (via
StreamMessageInputController(message: Message(parentId: parent!.id))) which
leads to the same disposal/leak issue as in tutorial_part_4.dart; refactor
ThreadPage from a StatelessWidget to a StatefulWidget, add a private
StreamMessageInputController field (initialized in initState using
Message(parentId: parent!.id) or using widget props), pass that controller into
StreamMessageComposer, and override dispose() to call controller.dispose() so
the controller is created once per widget instance and properly cleaned up.
In
`@packages/stream_chat_flutter/lib/src/components/message_composer/stream_chat_message_input.dart`:
- Around line 279-289: Clarify the inverted early-return in onLongPressCancel:
the guard currently reads "Return if the recording is already started" but this
callback should show the "hold to record" hint only when recording has NOT
started. Update the comment on the check in onLongPressCancel (and make it
symmetric with onLongPressStart) to state that if
audioRecorderController.isRecording is true we should bail because a recording
is already in progress, otherwise call
widget.feedback.onRecordStartCancel(context) and
audioRecorderController.showInfo(context.translations.holdToRecordLabel) to
inform the user they released before recording began; reference
onLongPressCancel, audioRecorderController.isRecording,
widget.feedback.onRecordStartCancel, audioRecorderController.showInfo and
context.translations.holdToRecordLabel when locating the change.
In
`@packages/stream_chat_flutter/lib/src/message_input/stream_message_composer.dart`:
- Around line 61-99: The constructor duplicates 30+ parameters between
StreamMessageComposer and MessageComposerProps; add a second constructor
StreamMessageComposer.fromProps({required MessageComposerProps props, Key? key})
(or change the public ctor to accept an optional props parameter) and wire that
constructor to set this.props directly so callers can pass a pre-built
MessageComposerProps instead of re-specifying every field; keep the existing
named-parameter convenience ctor but refactor it to build
MessageComposerProps(...) and forward to the new fromProps initializer to avoid
parameter duplication and ensure symbols StreamMessageComposer and
MessageComposerProps are used consistently.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: c5e14197-b508-429e-9ffb-356922ce3374
📒 Files selected for processing (36)
CLAUDE.mddocs/docs_screenshots/test/message_input/stream_message_composer_test.dartdocs/docs_screenshots/test/src/mocks.dartdocs/docs_screenshots/test/voice_recording/voice_recording_test.dartmigrations/redesign/message_composer.mdmigrations/v10-migration.mdpackages/stream_chat_flutter/README.mdpackages/stream_chat_flutter/example/lib/main.dartpackages/stream_chat_flutter/example/lib/split_view.dartpackages/stream_chat_flutter/example/lib/tutorial_part_1.dartpackages/stream_chat_flutter/example/lib/tutorial_part_2.dartpackages/stream_chat_flutter/example/lib/tutorial_part_3.dartpackages/stream_chat_flutter/example/lib/tutorial_part_4.dartpackages/stream_chat_flutter/example/lib/tutorial_part_5.dartpackages/stream_chat_flutter/example/lib/tutorial_part_6.dartpackages/stream_chat_flutter/lib/src/components/message_composer/message_composer.dartpackages/stream_chat_flutter/lib/src/components/message_composer/message_composer_component_props.dartpackages/stream_chat_flutter/lib/src/components/message_composer/message_composer_input.dartpackages/stream_chat_flutter/lib/src/components/message_composer/stream_chat_message_composer.dartpackages/stream_chat_flutter/lib/src/components/message_composer/stream_chat_message_input.dartpackages/stream_chat_flutter/lib/src/keyboard_shortcuts/keysets.dartpackages/stream_chat_flutter/lib/src/localization/translations.dartpackages/stream_chat_flutter/lib/src/message_input/attachment_picker/stream_attachment_picker_controller.dartpackages/stream_chat_flutter/lib/src/message_input/enums.dartpackages/stream_chat_flutter/lib/src/message_input/message_input_placeholder.dartpackages/stream_chat_flutter/lib/src/message_input/stream_message_composer.dartpackages/stream_chat_flutter/lib/src/message_list_view/message_list_view.dartpackages/stream_chat_flutter/lib/src/utils/typedefs.dartpackages/stream_chat_flutter/lib/stream_chat_flutter.dartpackages/stream_chat_flutter/test/src/message_input/message_input_test.dartpackages/stream_chat_localizations/example/lib/add_new_lang.dartpackages/stream_chat_localizations/example/lib/main.dartpackages/stream_chat_localizations/example/lib/override_lang.dartsample_app/lib/pages/channel_page.dartsample_app/lib/pages/new_chat_screen.dartsample_app/lib/pages/thread_page.dart
💤 Files with no reviewable changes (1)
- packages/stream_chat_flutter/lib/src/components/message_composer/stream_chat_message_composer.dart
| ### Removed parameters | ||
|
|
||
| Many parameters that existed in older versions of `StreamMessageInput` have been removed. The table below lists each removed parameter and the recommended migration path. | ||
| Many parameters that existed in older versions of `StreamMessageComposer` have been removed. The table below lists each removed parameter and the recommended migration path. |
There was a problem hiding this comment.
Misleading phrasing: parameters were in StreamMessageInput, not older StreamMessageComposer
The current wording implies the removed parameters once existed in a prior release of StreamMessageComposer, but StreamMessageComposer is the new name introduced by this very PR. A v9 or stable-SDK developer migrating here never used StreamMessageComposer; the parameters lived in StreamMessageInput.
📝 Suggested fix
-Many parameters that existed in older versions of `StreamMessageComposer` have been removed. The table below lists each removed parameter and the recommended migration path.
+Many parameters that existed in `StreamMessageInput` have been removed from `StreamMessageComposer`. The table below lists each removed parameter and the recommended migration path.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@migrations/redesign/message_composer.md` at line 87, The phrasing incorrectly
states the removed parameters were in an older StreamMessageComposer; update the
sentence and any related headings to state that the parameters previously
belonged to StreamMessageInput (the pre-migration type) and not
StreamMessageComposer (the new name introduced by this PR). Locate the sentence
"Many parameters that existed in older versions of `StreamMessageComposer` have
been removed." and change it to reference `StreamMessageInput`, and scan the
surrounding paragraph/table captions to ensure all mentions consistently say
"StreamMessageInput" (or "previous StreamMessageInput") as the source of the
removed parameters.
| /// The label for also send | ||
| /// as direct message "checkbox"" in [StreamMessageInput] | ||
| /// as direct message "checkbox"" in [StreamMessageComposer] | ||
| String get alsoSendAsDirectMessageLabel; |
There was a problem hiding this comment.
Fix doc typo in translation API comment.
Line 103 has an extra quote in checkbox"", which will leak into generated docs.
✏️ Suggested fix
- /// as direct message "checkbox"" in [StreamMessageComposer]
+ /// as direct message "checkbox" in [StreamMessageComposer]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| /// The label for also send | |
| /// as direct message "checkbox"" in [StreamMessageInput] | |
| /// as direct message "checkbox"" in [StreamMessageComposer] | |
| String get alsoSendAsDirectMessageLabel; | |
| /// The label for also send | |
| /// as direct message "checkbox" in [StreamMessageComposer] | |
| String get alsoSendAsDirectMessageLabel; |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/stream_chat_flutter/lib/src/localization/translations.dart` around
lines 102 - 104, Fix the typo in the doc comment for the getter
alsoSendAsDirectMessageLabel by removing the stray extra double-quote so the
sentence reads correctly (e.g., change 'checkbox""' to 'checkbox'); update the
three-line comment above String get alsoSendAsDirectMessageLabel; to ensure
generated docs don't contain the unintended quote.
| final removedIds = pickerIds.difference(messageIds); | ||
| if (removedIds.isEmpty) return; | ||
| final addedIds = messageIds.difference(pickerIds); | ||
|
|
||
| if (removedIds.isEmpty && addedIds.isEmpty) return; | ||
|
|
||
| final addedAttachments = addedIds | ||
| .map((id) => pickerController.value.attachments.firstWhere((a) => a.id == id)) | ||
| .toList(); | ||
|
|
||
| _isSyncingControllers = true; | ||
| try { | ||
| for (final id in removedIds) { | ||
| pickerController.removeAttachmentById(id); | ||
| } | ||
| for (final attachment in addedAttachments) { | ||
| pickerController.addAttachment(attachment); | ||
| } |
There was a problem hiding this comment.
Critical bug: addedAttachments looks up IDs in the wrong collection.
addedIds = messageIds.difference(pickerIds) are exactly the attachment IDs that exist in _effectiveController.attachments but not in pickerController.value.attachments. The subsequent firstWhere then searches the picker controller's attachments for those IDs and will throw a StateError for every added attachment because they are guaranteed to not be there.
The lookup must be done against the effective/message controller's attachments.
🐛 Proposed fix
final removedIds = pickerIds.difference(messageIds);
final addedIds = messageIds.difference(pickerIds);
if (removedIds.isEmpty && addedIds.isEmpty) return;
final addedAttachments = addedIds
- .map((id) => pickerController.value.attachments.firstWhere((a) => a.id == id))
+ .map((id) => _effectiveController.attachments.firstWhere((a) => a.id == id))
.toList();📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| final removedIds = pickerIds.difference(messageIds); | |
| if (removedIds.isEmpty) return; | |
| final addedIds = messageIds.difference(pickerIds); | |
| if (removedIds.isEmpty && addedIds.isEmpty) return; | |
| final addedAttachments = addedIds | |
| .map((id) => pickerController.value.attachments.firstWhere((a) => a.id == id)) | |
| .toList(); | |
| _isSyncingControllers = true; | |
| try { | |
| for (final id in removedIds) { | |
| pickerController.removeAttachmentById(id); | |
| } | |
| for (final attachment in addedAttachments) { | |
| pickerController.addAttachment(attachment); | |
| } | |
| final removedIds = pickerIds.difference(messageIds); | |
| final addedIds = messageIds.difference(pickerIds); | |
| if (removedIds.isEmpty && addedIds.isEmpty) return; | |
| final addedAttachments = addedIds | |
| .map((id) => _effectiveController.attachments.firstWhere((a) => a.id == id)) | |
| .toList(); | |
| _isSyncingControllers = true; | |
| try { | |
| for (final id in removedIds) { | |
| pickerController.removeAttachmentById(id); | |
| } | |
| for (final attachment in addedAttachments) { | |
| pickerController.addAttachment(attachment); | |
| } |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@packages/stream_chat_flutter/lib/src/message_input/stream_message_composer.dart`
around lines 1015 - 1031, The addedAttachments lookup is using
pickerController.value.attachments but addedIds are IDs present in
_effectiveController.attachments (message controller) and absent from the
picker, so firstWhere will throw; change the mapping that builds
addedAttachments to search _effectiveController.attachments (or the effective
controller's attachments collection used elsewhere in this file) instead of
pickerController.value.attachments so you retrieve the actual attachments to add
before calling pickerController.addAttachment for each.
| - [StreamChannelHeader](https://getstream.io/chat/docs/sdk/flutter/stream_chat_flutter/stream_channel_header/) | ||
| - [StreamChannelListView](https://getstream.io/chat/docs/sdk/flutter/stream_chat_flutter/stream_channel_list_view/) | ||
| - [StreamMessageInput](https://getstream.io/chat/docs/sdk/flutter/stream_chat_flutter/stream_message_input/) | ||
| - [StreamMessageComposer](https://getstream.io/chat/docs/sdk/flutter/stream_chat_flutter/stream_message_composer/) |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
https://getstream.io/chat/docs/sdk/flutter/stream_chat_flutter/stream_message_composer/ - does this page exist?
💡 Result:
No—the specific URL you provided does not appear to exist (or at least is not present in Stream’s current Flutter docs structure). The closest existing Flutter doc is for StreamMessageInput at https://getstream.io/chat/docs/sdk/flutter/stream_chat_flutter/message_composer/stream_message_input/ [1], which indicates that the message composer documentation lives under /message_composer/ but uses stream_message_input/ rather than stream_message_composer/ in the path [1]. Your URL: https://getstream.io/chat/docs/sdk/flutter/stream_chat_flutter/stream_message_composer/ was not found in the indexed results from Stream’s docs, while the existing related composer page under /message_composer/ was found [1].
Citations:
Fix the broken documentation link for StreamMessageComposer.
The URL https://getstream.io/chat/docs/sdk/flutter/stream_chat_flutter/stream_message_composer/ does not exist. Stream's composer documentation follows the pattern /message_composer/stream_message_input/ (e.g., https://getstream.io/chat/docs/sdk/flutter/stream_chat_flutter/message_composer/stream_message_input/). Verify the correct path for StreamMessageComposer docs and update the link accordingly.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/stream_chat_flutter/README.md` at line 102, Update the broken README
link for StreamMessageComposer: replace the non-existent URL ending with
/stream_message_composer/ with the correct Stream docs path following the
message_composer pattern (e.g., /message_composer/stream_message_input/), so the
README's StreamMessageComposer link points to the valid documentation page for
StreamMessageComposer/StreamMessageInput.
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## v10.0.0 #2642 +/- ##
===========================================
+ Coverage 67.13% 67.43% +0.29%
===========================================
Files 418 419 +1
Lines 25200 25217 +17
===========================================
+ Hits 16919 17004 +85
+ Misses 8281 8213 -68 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
renefloor
force-pushed
the
feature/rename-message-input
branch
from
5ed8948 to
976871d
Compare
1 participant
Submit a pull request
CLA
Description of the pull request
This renames the StreamMessageInput to StreamMessageComposer and the StreamChatMessageComposer to StreamChatMessageInput.
It also fixes the component builders and the attachment sync.
Summary by CodeRabbit
Release Notes
New Features
Updates