refactor: rename FlowChatScreen to FlowChatView - #14
Merged
Conversation
rahulbisht25
approved these changes
Aug 20, 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.
Summary
FlowChatScreenis nowFlowChatView. The widget was never a screen: it builds noScaffoldand no app bar, and its docs have always said to drop it in a scaffold body. With SidePanel and Modal on the roadmap it is the surface hosts will embed inside them, so the name now follows Flutter's convention for embeddable composites (TabBarView,PageView).Everything the name touched moves with it:
flow_chat_screen.dartis nowflow_chat_view.dart, with the export and all doc comment cross references updatedcomponents/chat-screentocomponents/chat-view, with a redirect from the old URL so existing links keep workingProse that refers to the host's own screen (like the README's "Build a chat screen") is unchanged on purpose: the host builds the screen, flow_ui provides the view.
How this was verified
flutter analyzeclean in the package root,example/, andplayground/dart format .produced no changesnpm run buildindocs/passes, and the emitted redirect page at/components/chat-screenpoints to/components/chat-viewChecklist
flutter analyze libandflutter analyzeinexample/andplayground/are cleandart format .applieddependencies:inpubspec.yaml(Flutter SDK and flutter.dev packages only)lib/flow_ui.dartand documented indocs/and the README tableCHANGELOG.mdupdated for user-facing changes, with breaking changes called outfeat:,fix:,refactor:,docs:,chore:)Note
Medium Risk
Public API rename with no behavior change, but it is a breaking call-site update for every host using the chat surface.
Overview
Breaking rename:
FlowChatScreenis nowFlowChatView. The widget was never a screen (body-only, noScaffold), and the name now matches Flutter’s embeddable-composite convention ahead of SidePanel/Modal.The class, file (
flow_chat_view.dart), barrel export, example, playground, README, and component docs all move with it. Docs live at/components/chat-view, with a redirect from/components/chat-screen. Constructor and behavior are unchanged — hosts only need to rename call sites.Reviewed by Cursor Bugbot for commit 81244a5. Bugbot is set up for automated code reviews on this repo. Configure here.