feat: rename ChannelPaginatorsOrchestrator to ChannelManager - #3258
Conversation
|
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 Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-v15 #3258 +/- ##
==============================================
Coverage ? 84.15%
==============================================
Files ? 523
Lines ? 15900
Branches ? 5047
==============================================
Hits ? 13380
Misses ? 2520
Partials ? 0 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Chat no longer constructs a ChannelManager or a default paginator; it exposes
`client.channelManager` on ChatContext and leaves list registration to the
application.
BREAKING CHANGE: the `channelManager` prop is removed and no `channels:default`
paginator is created. Register lists with
`client.channelManager.insertPaginator({ paginator })`.
The paginator outlives the component now, so querying only on mount left a list reset by a disconnect permanently empty. Drive the query off the reactive "never queried" state instead; a loaded-but-empty page still does not auto-query.
Both examples register their paginators on the client-owned manager instead of passing a ChannelManager to <Chat>. The vite example sets its ownership priority there too and drops its custom mute handler, now a default in the LLC, and the remaining `orchestrator` naming follows the rename.
🎯 Goal
depends on GetStream/stream-chat-js#1813
Tracks the stream-chat rename of ChannelPaginatorsOrchestrator to
ChannelManager. No behavioral change on the React side.
BREAKING CHANGE: the prop and the ChatContext field
channelPaginatorsOrchestrator are renamed to channelManager, and the types
ChannelPaginatorsOrchestrator / ChannelPaginatorsOrchestratorState are now
ChannelManager / ChannelManagerState. Every useChatContext() consumer reading
the old field, and any test that builds a partial ChatContext value, has to be
updated. No deprecated prop or type aliases are exported.