Skip to content

Commit 30a516a

Browse files
authored
docs: track react v14 dialog and reactions follow-up (#3071)
### 🎯 Goal Keep the internal React v14 migration trackers aligned with the latest docs and source changes around dialog/context-menu behavior, `useChannelListContext()`, and reactions-detail behavior. ### 🛠 Implementation details - advance the audited SDK head to `55b1dd6c` - add `BC-056` for the `useChannelListContext()` signature cleanup - record the latest dialog/context-menu and reactions-detail refinements in the tracker files - resolve the matching docs-plan issues now that the public docs are updated in docs-content#1125 ### 🎨 UI Changes None. ### Validation - `git diff --check`
1 parent 277bc41 commit 30a516a

2 files changed

Lines changed: 162 additions & 103 deletions

File tree

ai-docs/breaking-changes.md

Lines changed: 32 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# React v14 Breaking Changes
22

3-
Last updated: 2026-03-25
3+
Last updated: 2026-03-27
44

55
## Scope
66

@@ -13,8 +13,8 @@ This file tracks confirmed v13 to v14 breaking changes for `stream-chat-react`.
1313
## Audit Reference
1414

1515
- Baseline tag: `v13.14.2`
16-
- Current audited SDK head: `9877da511183c5149959583bc4f11d7aa616f87f` (`9877da51`, `2026-03-25`, `chore: migrate test suite from JavaScript to TypeScript (#3057)`)
17-
- Future mining starting point: diff `9877da511183c5149959583bc4f11d7aa616f87f..HEAD` first, then compare any newly confirmed changes back to the original v13 baseline before adding them here
16+
- Current audited SDK head: `55b1dd6c43f006ac8e7e2ceba1a58d8838bef149` (`55b1dd6c`, `2026-03-27`, `chore(release): 14.0.0-beta.3 [skip ci]`)
17+
- Future mining starting point: diff `55b1dd6c43f006ac8e7e2ceba1a58d8838bef149..HEAD` first, then compare any newly confirmed changes back to the original v13 baseline before adding them here
1818

1919
Only confirmed items should move from this file into the migration guide.
2020

@@ -1915,6 +1915,32 @@ Only confirmed items should move from this file into the migration guide.
19151915
- `docs/data/docs/chat-sdk/react/v14/04-guides/05-channel_read_state.md`
19161916
- Example needed: yes
19171917

1918+
### BC-056: `useChannelListContext()` no longer accepts a diagnostic component name
1919+
1920+
- Status: confirmed
1921+
- Area: channel-list hooks
1922+
- User impact:
1923+
- TypeScript code calling `useChannelListContext('MyComponent')` no longer type-checks
1924+
- integrations that relied on the SDK's outside-provider console warning no longer get that diagnostic side effect
1925+
- custom docs/snippets that still describe `componentName` as part of the hook signature are stale
1926+
- Old API:
1927+
- `v13.14.2:src/context/ChannelListContext.tsx:41` exported `useChannelListContext(componentName?: string)`
1928+
- `9877da51:src/context/ChannelListContext.tsx:41` still logged the missing-provider warning and interpolated `componentName`
1929+
- New API:
1930+
- `src/context/ChannelListContext.tsx:44` exports `useChannelListContext()` with no parameters
1931+
- `src/context/ChannelListContext.tsx:47` through `:49` now return an empty context object outside the provider without logging
1932+
- Replacement:
1933+
- call `useChannelListContext()` without arguments
1934+
- do not rely on SDK warnings for provider misuse; add app-owned assertions or logging if you still need that diagnostic signal
1935+
- Evidence:
1936+
- commit `7914e516 feat: reset audio player progress when the track is fully played (#3066)` removed the optional `componentName` parameter and the warning branch from `useChannelListContext()`
1937+
- current source keeps the hook public, but its signature and missing-provider behavior no longer match v13 or the previously audited v14 snapshots
1938+
- Docs impact:
1939+
- migration guide
1940+
- `docs/data/docs/chat-sdk/react/v14/02-ui-components/05-channel-list/02-channel_list_context.md`
1941+
- `docs/data/docs/chat-sdk/react/v14/04-guides/07-sdk-state-management.md`
1942+
- Example needed: no
1943+
19181944
## Likely
19191945

19201946
- None yet
@@ -1933,6 +1959,9 @@ Only confirmed items should move from this file into the migration guide.
19331959
- composer clear-on-unmount (`f2a79ab1`): investigated; `TextareaComposer` now clears composer state on unmount, but there is no removed export, renamed prop, or new override-key migration to track separately.
19341960
- shared attachment preview gallery (`f05f47d7`): investigated; `AttachmentPreviewList` now shares gallery preview behavior across attachments, but this is current UI behavior rather than a removed or renamed public API.
19351961
- voice-message deleted notification (`9982c45a`): investigated; this adds a new default notification string/behavior for deleted voice recordings, but it does not remove or rename the existing public attachment APIs.
1962+
- context-menu animations and global outside-click dismissal controls (`630e5c72`): investigated; current source adds `ContextMenu`, `ContextMenuContent`, `DialogManagerProvider.closeOnClickOutside`, and `DialogAnchor` transition controls, but this is additive customization and behavior polish rather than a removed or renamed v13 public API.
1963+
- `MessageReactionsDetail` loading/toggle refinements (`cab3ffd3`): investigated; current source adds `MessageReactionsDetailLoadingIndicator`, allows toggling the selected reaction type back to `null`, and improves the unfiltered reactions view, but these are additive/current-behavior changes rather than a distinct migration bucket.
1964+
- audio/player, scrolling, and layout polish (`7914e516`, `91eba1b4`, `8d25ead3`, `55dd2e81`, `fdf0e155`, `221aa0d4`): investigated; these commits refine playback reset behavior, initial bottom-pinning, mobile-nav click detection, message-list width, reactions alignment, and voice-recording attachment layout, but they do not remove or rename a documented public API beyond the separately tracked `useChannelListContext()` signature cleanup.
19361965

19371966
## Notes For Migration Guide Drafting
19381967

0 commit comments

Comments
 (0)