stream-chat-react-native-core 10.0.0-rc.1 → 10.0.0-rc.2

package/src/contexts/messagesContext/MessagesContext.tsx

@@ -38,43 +38,37 @@ export type MessageLocationProps = {
 };
 
 export type MessagesContextValue = {
-  /** Should keyboard be dismissed when messaged is touched */
+  /** Whether touching a message dismisses the keyboard. */
   dismissKeyboardOnMessageTouch: boolean;
 
   enableMessageGroupingByUser: boolean;
 
-  /**
-   * The type of URL preview to render.
-   * Defaults to: 'full'
-   */
+  /** The type of URL preview to render. Defaults to 'full'. */
   urlPreviewType: 'compact' | 'full';
 
   FlatList: typeof NativeHandlers.FlatList | undefined;
   /**
-   * The giphy version to render - check the keys of the [Image Object](https://developers.giphy.com/docs/api/schema#image-object) for possible values. Uses 'fixed_height' by default
-   * */
+   * The Giphy image version to render, one of the keys of the Giphy
+   * [Image Object](https://developers.giphy.com/docs/api/schema#image-object).
+   * Defaults to 'fixed_height'.
+   */
   giphyVersion: keyof NonNullable<Attachment['giphy']>;
 
-  /** Order to render the message content */
+  /** Order in which the message content types are rendered. */
   messageContentOrder: MessageContentType[];
   /**
-   * Overlay target id that should be teleported when a message overlay opens.
-   * Custom `MessageOverlayWrapper` usages should pass a matching `targetId`.
+   * Overlay target ID to teleport when a message overlay opens. A custom `MessageOverlayWrapper`
+   * needs a matching `targetId`.
    */
   messageOverlayTargetId?: string;
   /**
-   * Provide any additional props for `Pressable` which wraps inner MessageContent component here.
-   * Please check docs for Pressable for supported props - https://reactnative.dev/docs/pressable#props
+   * Extra props for the `Pressable` that wraps the inner `MessageContent`, except `style`.
    *
    * @overrideType Object
    */
   additionalPressableProps?: Omit<PressableProps, 'style'>;
 
-  /**
-   * Custom handler to handle message swipe action.
-   *
-   * The default behaviour is swipe to reply for this.
-   */
+  /** Overrides the swipe action on a message, which quotes the message by default. */
   customMessageSwipeAction?: ({
     channel,
     message,
@@ -84,204 +78,85 @@ export type MessagesContextValue = {
   }) => void;
 
   disableTypingIndicator?: boolean;
-  /**
-   * Enable swipe to reply on messages.
-   */
+  /** Whether swiping a message replies to it. Defaults to true. */
   enableSwipeToReply?: boolean;
   /**
-   * Whether messages should be aligned to right or left part of screen.
-   * By default, messages will be received messages will be aligned to left and
-   * sent messages will be aligned to right.
+   * Forces every message to the 'left' or 'right' side of the screen. By default, received messages
+   * are on the left and sent messages on the right.
    */
   forceAlignMessages?: Alignment | boolean;
 
   getMessageGroupStyle?: (params: MessageGroupStylesParams) => GroupStyle[];
   /**
-   * Handler to access when a ban user action is invoked.
+   * Called when the ban user action runs, before the default action.
    * @param message
    */
   handleBan?: (message: LocalMessage) => Promise<void>;
-  /** Handler to access when a copy message action is invoked */
+  /** Called when the copy message action runs, before the default action. */
   handleCopy?: (message: LocalMessage) => Promise<void>;
-  /** Handler to access when a delete for me message action is invoked */
+  /** Called when the delete for me action runs, before the default action. */
   handleDeleteForMe?: (message: LocalMessage) => Promise<void>;
-  /** Handler to access when a delete message action is invoked */
+  /** Called when the delete message action runs, before the default action. */
   handleDelete?: (message: LocalMessage) => Promise<void>;
-  /** Handler to access when an edit message action is invoked */
+  /** Called when the edit message action runs, before the default action. */
   handleEdit?: (message: LocalMessage) => void;
-  /** Handler to access when a flag message action is invoked */
+  /** Called when the flag message action runs, before the default action. */
   handleFlag?: (message: LocalMessage) => Promise<void>;
-  /** Handler to access when a mark unread action is invoked */
+  /** Called when the mark unread action runs, before the default action. */
   handleMarkUnread?: (message: LocalMessage) => Promise<void>;
-  /** Handler to access when a mute user action is invoked */
+  /** Called when the mute user action runs, before the default action. */
   handleMute?: (message: LocalMessage) => Promise<void>;
-  /** Handler to access when a pin/unpin user action is invoked*/
+  /** Called when the pin/unpin action runs, before the default action. */
   handlePinMessage?: ((message: LocalMessage) => MessageActionType) | null;
-  /** Handler to access when a quoted reply action is invoked */
+  /** Called when the quoted reply action runs, before the default action. */
   handleQuotedReply?: (message: LocalMessage) => Promise<void>;
-  /** Handler to process a reaction */
+  /** Called when a reaction is toggled, before the default action. */
   handleReaction?: (message: LocalMessage, reactionType: string) => Promise<void>;
-  /** Handler to access when a retry action is invoked */
+  /** Called when the retry action runs, with the message stripped of reserved fields. */
   handleRetry?: (message: LocalMessage) => Promise<void>;
-  /** Handler to access when a thread reply action is invoked */
+  /** Called when the thread reply action runs, before the default action. */
   handleThreadReply?: (message: LocalMessage) => Promise<void>;
-  /** Handler to access when a blocking user action is invoked */
+  /** Called when the block user action runs, before the default action. */
   handleBlockUser?: (user: LocalMessage['user']) => Promise<void>;
-  /** A flag specifying whether the poll creation button is available or not. */
+  /** Whether the poll creation button is available. Also requires polls enabled on the channel. */
   hasCreatePoll?: boolean;
-  /** Handler to deal with custom memoization logic of Attachment */
+  /** Custom memoization check for an attachment: returns whether the two are equal. */
   isAttachmentEqual?: (prevAttachment: Attachment, nextAttachment: Attachment) => boolean;
-  /** Object specifying rules defined within simple-markdown https://github.com/Khan/simple-markdown#adding-a-simple-extension */
+  /**
+   * Custom rules for the markdown renderer, as defined by simple-markdown:
+   * https://github.com/Khan/simple-markdown#adding-a-simple-extension
+   */
   markdownRules?: MarkdownRules;
   /**
-   * Use this prop to override message actions (which pop-up in message overlay).
-   *
-   * You can either completely override the default messageActions object.
+   * Overrides the message actions shown in the message overlay. Receives the default actions and
+   * returns the ones to show, in order. For example, to keep only two of them:
    *
    * ```
-   * <Channel
-   *   messageActions=[
-   *     {
-   *       action: () => { someAction() };
-   *       title: "Pin Message";
-   *       icon: PinIcon;
-   *       titleStyle: {};
-   *     },
-   *     {
-   *       action: () => { someAction() };
-   *       title: "Delete Message";
-   *       icon: PinIcon;
-   *       titleStyle: {};
-   *     }
-   *   ]
-   * >
-   * </Channel>
+   * <Channel messageActions={({ copyMessage, threadReply }) => [threadReply, copyMessage]} />
    * ```
    *
-   * Or you can selectly keep certain action and remove some:
-   *
-   * e.g. Lets say you only want to keep threadReply and copyMessage actions
-   *
-   * ```
-   * <Channel
-   *   messageActions={({
-   *     banUser,
-   *     blockUser,
-   *     copyMessage,
-   *     deleteMessage,
-   *     editMessage,
-   *     flagMessage,
-   *     markUnread,
-   *     muteUser,
-   *     quotedReply,
-   *     retry,
-   *     threadReply,
-   *   }) => ([
-   *     threadReply, copyMessage
-   *   ])}
-   * >
-   *  </Channel>
-   *  ```
-   *
    * @overrideType Function | Array<Objects>
    */
   messageActions?: (param: MessageActionsParams) => MessageActionType[];
 
-  /**
-   * HitSlop for the message swipe to reply gesture
-   */
+  /** Hit slop of the swipe to reply gesture. */
   messageSwipeToReplyHitSlop?: ViewProps['hitSlop'];
-  /**
-   * The number of lines of the message text to be displayed
-   */
+  /** Maximum number of lines of message text to display. Only the first paragraph is rendered. */
   messageTextNumberOfLines?: number;
-  /**
-   * Theme provided only to messages that are the current users
-   */
+  /** Theme applied only to the messages of the current user. */
   myMessageTheme?: DeepPartial<Theme>;
   /**
-   * Override default handler for onLongPress on message. You have access to payload of that handler as param:
-   *
-   * ```
-   * <Channel
-   *  onLongPressMessage={({
-   *    actionHandlers: {
-   *        deleteMessage, // () => Promise<void>;
-   *        editMessage, // () => void;
-   *        quotedReply, // () => void;
-   *        resendMessage, // () => Promise<void>;
-   *        showMessageOverlay, // () => void;
-   *        toggleBanUser, // () => Promise<void>;
-   *        toggleMuteUser, // () => Promise<void>;
-   *        toggleReaction, // (reactionType: string) => Promise<void>;
-   *    },
-   *    defaultHandler, // () => void
-   *    event, // any event object corresponding to touchable feedback
-   *    emitter, // which component trigged this touchable feedback e.g. card, fileAttachment, gallery, message ... etc
-   *    message // message object on which longPress occured
-   *  }) => {
-   *    // Your custom action
-   *  }}
-   * />
-   * ```
+   * Overrides the long press handler of a message, which opens the message overlay by default. The
+   * payload carries `actionHandlers`, `defaultHandler`, `emitter`, `event` and `message`.
    */
   onLongPressMessage?: (payload: MessagePressableHandlerPayload) => void;
-  /**
-   * Add onPressIn handler for attachments. You have access to payload of that handler as param:
-   *
-   * ```
-   * <Channel
-   *  onPressInMessage={({
-   *    actionHandlers: {
-   *        deleteMessage, // () => Promise<void>;
-   *        editMessage, // () => void;
-   *        quotedReply, // () => void;
-   *        resendMessage, // () => Promise<void>;
-   *        showMessageOverlay, // () => void;
-   *        toggleBanUser, // () => Promise<void>;
-   *        toggleMuteUser, // () => Promise<void>;
-   *        toggleReaction, // (reactionType: string) => Promise<void>;
-   *    },
-   *    defaultHandler, // () => void
-   *    event, // any event object corresponding to touchable feedback
-   *    emitter, // which component trigged this touchable feedback e.g. card, fileAttachment, gallery, message ... etc
-   *    message // message object on which longPress occured
-   *  }) => {
-   *    // Your custom action
-   *  }}
-   * />
-   * ```
-   */
+  /** Called when a press on a message or its content starts. Takes the same payload. */
   onPressInMessage?: (payload: MessagePressableHandlerPayload) => void;
   /**
-   * Override onPress handler for message. You have access to payload of that handler as param:
-   *
-   * ```
-   * <Channel
-   *  onPressMessage={({
-   *    actionHandlers: {
-   *        deleteMessage, // () => Promise<void>;
-   *        editMessage, // () => void;
-   *        quotedReply, // () => void;
-   *        resendMessage, // () => Promise<void>;
-   *        showMessageOverlay, // () => void;
-   *        toggleBanUser, // () => Promise<void>;
-   *        toggleMuteUser, // () => Promise<void>;
-   *        toggleReaction, // (reactionType: string) => Promise<void>;
-   *    },
-   *    additionalInfo, // emitter-specific info, e.g. `{ reactionType }` when emitter === 'reactionList'
-   *    defaultHandler, // () => void
-   *    event, // any event object corresponding to touchable feedback
-   *    emitter, // which component trigged this touchable feedback e.g. card, fileAttachment, gallery, message ... etc
-   *    message // message object on which longPress occurred
-   *  }) => {
-   *    // Your custom action
-   *  }}
-   * />
-   * ```
+   * Overrides the press handler of a message. Takes the same payload as `onLongPressMessage`.
    *
-   * By default, pressing a reaction opens the reactions bottom sheet. To instead toggle
-   * the reaction (add/remove the current user's reaction), intercept the `reactionList` emitter:
+   * Pressing a reaction opens the reactions bottom sheet by default. To toggle the reaction
+   * instead, intercept the `reactionList` emitter:
    *
    * ```
    * <Channel
@@ -297,35 +172,26 @@ export type MessagesContextValue = {
    */
   onPressMessage?: (payload: MessagePressableHandlerPayload) => void;
   /**
-   * Handles a press on the "Also sent in channel" / "Replied to a thread" header's "View" action.
-   * Inside a thread the payload carries the targeted message id; in a channel it also carries the
-   * reply's thread.
+   * Handles a press on the "View" action of the "Also sent in channel" / "Replied to a thread"
+   * header. The action is only shown when this is set. The payload carries the targeted message ID,
+   * and in a channel also the reply's thread.
    */
   onAlsoSentToChannelHeaderPress?: (payload: AlsoSentToChannelHeaderPressPayload) => void;
-  /**
-   * The position of the reaction list in the message
-   */
+  /** Where the reaction list renders in the message. Defaults to 'top'. */
   reactionListPosition?: 'top' | 'bottom';
 
-  /**
-   * The alignment of the reaction list
-   */
+  /** The layout of the reaction list. Defaults to 'clustered'. */
   reactionListType?: 'clustered' | 'segmented';
 
   /**
-   * Full override of the reaction function on Message and Message Overlay
-   *
-   * Please check [cookbook](https://github.com/GetStream/stream-chat-react-native/wiki/Cookbook-v3.0#override-or-intercept-message-actions-edit-delete-reaction-reply-etc) for details.
-   * */
+   * Overrides the reaction handler of the message and the message overlay: takes the message and
+   * returns the function that receives the reaction type.
+   */
   selectReaction?: (message: LocalMessage) => (reactionType: string) => Promise<void>;
 
-  /**
-   * Boolean to enable/disable the message underlay background when there are unread messages in the Message List.
-   */
+  /** Whether messages get an underlay when the list has unread ones. Defaults to true. */
   shouldShowUnreadUnderlay?: boolean;
-  /**
-   * The supported reactions that the user can use to react to messages.
-   */
+  /** The reactions users can react to messages with. */
   supportedReactions?: ReactionData[];
 };
 
@@ -349,7 +215,7 @@ export const useMessagesContext = () => {
 
   if (contextValue === DEFAULT_BASE_CONTEXT_VALUE && !isTestEnvironment()) {
     throw new Error(
-      'The useMessagesContext hook was called outside of the MessagesContext provider. Make sure you have configured MessageList component correctly - https://getstream.io/chat/docs/sdk/reactnative/basics/hello_stream_chat/#message-list',
+      'The useMessagesContext hook was called outside of the MessagesContext provider. Make sure you have configured Channel component correctly - https://getstream.io/chat/docs/sdk/react-native/core-components/channel/',
     );
   }
 

package/src/contexts/overlayContext/ClosingPortalHostsLayer.tsx

@@ -45,14 +45,9 @@ const ClosingPortalHostSlot = ({
 
 type ClosingPortalHostsLayerProps = {
   closeCoverOpacity: SharedValue<number>;
-  /**
-   * Id of the owning host layer, used to park the slot hosts while that layer is not the top one.
-   */
+  /** ID of the owning host layer, which parks the slot hosts when it is not the top one. */
   hostLayerId?: string;
-  /**
-   * Whether the owning host layer is the top one. Slots of any other layer park their hosts under
-   * names unique to that layer, so they never take the shared names from the top layer.
-   */
+  /** Whether the owning host layer is the top one. Other layers park hosts under unique names. */
   isTopHostLayer?: boolean;
 };
 

package/src/contexts/overlayContext/MessageOverlayHostLayer.tsx

@@ -72,10 +72,7 @@ export type MessageActionsProps = {
 };
 
 type MessageOverlayHostLayerProps = {
-  /**
-   * Id under which this layer registers on the host layer stack. `OverlayProvider` passes its own
-   * so that views inside the provider can tell whether this layer is the top one.
-   */
+  /** ID under which this layer registers on the host layer stack. */
   hostLayerId: string;
 };
 
@@ -94,10 +91,8 @@ export const MessageOverlayHostLayer = ({ hostLayerId }: MessageOverlayHostLayer
   const closeCorrectionY = useSharedValue(0);
 
   const topInset = insets.top;
-  // Due to edge-to-edge in combination with various libraries, Android sometimes reports
-  // the insets to be 0. If that's the case, we use this as an escape hatch to offset the bottom
-  // of the overlay so that it doesn't collide with the navigation bar. Worst case scenario,
-  // if the navigation bar is actually 0 - we end up animating a little bit further.
+  // With edge-to-edge, Android sometimes reports a bottom inset of 0. The fallback offset keeps the
+  // overlay clear of the navigation bar; if the bar really is 0, it animates slightly further.
   const bottomInset = insets.bottom === 0 && Platform.OS === 'android' ? 60 : insets.bottom;
 
   const isActive = !!id && isTop;
@@ -129,11 +124,8 @@ export const MessageOverlayHostLayer = ({ hostLayerId }: MessageOverlayHostLayer
     return () => subscription.remove();
   }, [isActive]);
 
-  // When orientation changes, we dismiss the overlay. While it is possible
-  // (and I have a working PoC of) a repositioning solution, it is pretty
-  // complex and probably bug prone. This is anyway how the iOS native contextual
-  // menu works (as seen on iMessage and Twitch for example, which support landscape
-  // mode).
+  // The overlay is dismissed on orientation change: repositioning is complex and error prone, and
+  // the iOS native context menu behaves the same way.
   const orientation = useScreenOrientation();
   const prevOrientationRef = useRef(orientation);
   useEffect(() => {
@@ -175,8 +167,8 @@ export const MessageOverlayHostLayer = ({ hostLayerId }: MessageOverlayHostLayer
     return Math.max(0, contentH - available);
   });
 
-  // On close, freeze any inflight fling (the message closes from where it was scrolled - see
-  // `hostStyle`) and only reset the offset once fully closed, ready for the next open.
+  // On close, freeze any in-flight fling (the message closes from where it was scrolled, see
+  // `hostStyle`); the offset resets only once fully closed.
   useEffect(() => {
     if (closing) {
       cancelAnimation(scrollY);
@@ -316,9 +308,9 @@ export const MessageOverlayHostLayer = ({ hostLayerId }: MessageOverlayHostLayer
     };
   });
 
-  // Two composed `translateY`: first is the springed open/close position, second is the raw
-  // scroll offset. On close we fold the scroll into the first (springed) target so the message
-  // animates back from where it was scrolled, while the latter stays put.
+  // Two composed `translateY`: the first is the springed open/close position, the second the raw
+  // scroll offset. On close the scroll folds into the springed target so the message animates back
+  // from where it was scrolled, while the raw offset stays put.
   const hostStyle = useAnimatedStyle(() => {
     if (!messageH.value) return { height: 0 };
     const scroll = scrollGeom.value.needsScroll ? scrollY.value : 0;
@@ -341,7 +333,7 @@ export const MessageOverlayHostLayer = ({ hostLayerId }: MessageOverlayHostLayer
   });
 
   // Drag scrolls the message (clamped to `[0, maxScroll]`); release flings with decay. When the
-  // content fits, `maxScroll` is 0 so this is a noop.
+  // content fits, `maxScroll` is 0 and this does nothing.
   const pan = useMemo(
     () =>
       Gesture.Pan()
@@ -434,8 +426,8 @@ export const MessageOverlayHostLayer = ({ hostLayerId }: MessageOverlayHostLayer
           ) : (
             <>
               {/*
-                Message renders first (lowest z) so it sits behind the opaque top/bottom items;
-                a scrolled/overflowing message passes behind them instead of being clipped.
+                The message renders first (lowest z) so an overflowing message scrolls behind the
+                opaque top and bottom items rather than being clipped.
               */}
               <GestureDetector gesture={pan}>
                 <Animated.View style={hostStyle} testID='message-overlay-message'>

package/src/contexts/overlayContext/OverlayContext.tsx

@@ -26,12 +26,11 @@ export const OverlayContext = React.createContext(
 
 export type OverlayProviderProps = ImageGalleryProviderProps & {
   /**
-   * Opt-in accessibility configuration. A11y is OFF by default — pass
-   * `accessibility={{ enabled: true }}` to enable screen-reader announcements,
-   * gesture alternatives, and semantic a11y attributes across the SDK.
+   * Opt-in accessibility configuration. Disabled by default; `accessibility={{ enabled: true }}`
+   * turns on screen-reader announcements, gesture alternatives and semantic a11y attributes.
    */
   accessibility?: AccessibilityConfig;
-  /** https://github.com/GetStream/stream-chat-react-native/wiki/Internationalization-(i18n) */
+  /** The `Streami18n` instance that enables internationalization. */
   i18nInstance?: Streami18n;
   value?: Partial<OverlayContextValue>;
 };
@@ -41,7 +40,7 @@ export const useOverlayContext = () => {
 
   if (contextValue === DEFAULT_BASE_CONTEXT_VALUE && !isTestEnvironment()) {
     throw new Error(
-      'The useOverlayContext hook was called outside the OverlayContext Provider. Make sure you have configured OverlayProvider component correctly - https://getstream.io/chat/docs/sdk/reactnative/basics/hello_stream_chat/#overlay-provider',
+      'The useOverlayContext hook was called outside the OverlayContext Provider. Make sure you have configured OverlayProvider component correctly - https://getstream.io/chat/docs/sdk/react-native/core-components/overlay-provider/',
     );
   }
 

package/src/contexts/overlayContext/OverlayHostLayerContext.ts

@@ -1,7 +1,7 @@
 import React, { useContext } from 'react';
 
 /**
- * The id of the `MessageOverlayHostLayer` rendered by the nearest `OverlayProvider`. Views that
+ * The ID of the `MessageOverlayHostLayer` rendered by the nearest `OverlayProvider`. Views that
  * teleport into that layer use it to tell whether their provider currently owns the overlay.
  */
 export const OverlayHostLayerContext = React.createContext<string | undefined>(undefined);

package/src/contexts/overlayContext/OverlayProvider.tsx

@@ -26,22 +26,8 @@ import {
 } from '../translationContext/TranslationContext';
 
 /**
- * - The highest level of these components is the `OverlayProvider`. The `OverlayProvider` allows users to interact with messages on long press above the underlying views, use the full screen image viewer, and use the `AttachmentPicker` as a keyboard-esk view.
- *  Because these views must exist above all others `OverlayProvider` should wrap your navigation stack as well. Assuming [`React Navigation`](https://reactnavigation.org/) is being used, your highest level navigation stack should be wrapped in the provider:
- *
- *    ```js
- *    <NavigationContainer>
- *      <OverlayProvider>
- *        <Stack.Navigator>
- *          <Stack.Screen />
- *        </Stack.Navigator>
- *      </OverlayProvider>
- *    </NavigationContainer>
- *    ```
- *
- * - Don't forget to check our cookbook section of [OverlayProvider](https://github.com/GetStream/stream-chat-react-native/wiki/Cookbook-v3.0#overlayprovider)
- *
- * - Also check the [visual component guide](https://github.com/GetStream/stream-chat-react-native/wiki/Cookbook-v3.0#custom-components), to learn about component customizations.
+ * Hosts the message overlay and the full screen image gallery above the rest of the tree, so it
+ * must wrap the whole navigation stack (inside `NavigationContainer` with React Navigation).
  *
  * @example ./OverlayProvider.md
  */
@@ -61,7 +47,6 @@ export const OverlayProvider = (props: PropsWithChildren<OverlayProviderProps>)
 
   const overlayOpacity = useSharedValue(0);
 
-  // Setup translators
   const translators = useStreami18n(i18nInstance);
 
   useEffect(() => {

package/src/contexts/ownCapabilitiesContext/OwnCapabilitiesContext.tsx

@@ -49,7 +49,7 @@ export const useOwnCapabilitiesContext = () => {
 
   if (contextValue === DEFAULT_BASE_CONTEXT_VALUE && !isTestEnvironment()) {
     throw new Error(
-      'The useOwnCapabilitiesContext hook was called outside the Channel Component. Make sure you have configured Channel component correctly - https://getstream.io/chat/docs/sdk/reactnative/basics/hello_stream_chat/#channel',
+      'The useOwnCapabilitiesContext hook was called outside the Channel Component. Make sure you have configured Channel component correctly - https://getstream.io/chat/docs/sdk/react-native/core-components/channel/',
     );
   }
 

package/src/contexts/pollContext/createPollContentContext.tsx

@@ -16,11 +16,7 @@ export type CreatePollContentContextValue = {
   sendMessage: MessageInputContextValue['sendMessage'];
   closePollCreationDialog?: () => void;
   modalStateStore?: StateStore<CreatePollModalState>;
-  /**
-   * Vertical gap between poll options in the poll creation screen.
-   *
-   * **Default: ** 8
-   */
+  /** Vertical gap between poll options in the poll creation screen. Defaults to 8. */
   createPollOptionGap?: number;
 };
 
@@ -46,7 +42,7 @@ export const useCreatePollContentContext = () => {
 
   if (contextValue === DEFAULT_BASE_CONTEXT_VALUE && !isTestEnvironment()) {
     throw new Error(
-      'The useCreatePollContentContext hook was called outside of the CreatePollContentContext provider. Make sure you have configured the CreatePollContent component correctly - https://getstream.io/chat/docs/sdk/reactnative/basics/hello_stream_chat/#channel',
+      'The useCreatePollContentContext hook was called outside of the CreatePollContentContext provider. Make sure you have configured the CreatePoll component correctly - https://getstream.io/chat/docs/sdk/react-native/ui-components/create-poll/',
     );
   }
 

package/src/contexts/pollContext/pollContext.tsx

@@ -29,7 +29,7 @@ export const usePollContext = () => {
 
   if (contextValue === DEFAULT_BASE_CONTEXT_VALUE && !isTestEnvironment()) {
     throw new Error(
-      'The usePollContext hook was called outside of the PollContext provider. Make sure you have configured the Poll component correctly - https://getstream.io/chat/docs/sdk/reactnative/basics/hello_stream_chat/#channel',
+      'The usePollContext hook was called outside of the PollContext provider. Make sure you have configured the Poll component correctly - https://getstream.io/chat/docs/sdk/react-native/ui-components/poll/',
     );
   }
 

package/src/contexts/screenReaderContext/ScreenReaderContext.tsx

@@ -4,7 +4,7 @@ import { AccessibilityInfo } from 'react-native';
 import { useAccessibilityContext } from '../accessibilityContext/AccessibilityContext';
 
 export type ScreenReaderContextValue = {
-  /** True when an OS screen reader (VoiceOver / TalkBack) is currently active. */
+  /** Whether an OS screen reader (VoiceOver or TalkBack) is active. */
   enabled: boolean;
 };
 
@@ -15,12 +15,8 @@ export const ScreenReaderContext = React.createContext<ScreenReaderContextValue>
 );
 
 /**
- * Owns the single, app wide screen reader subscription. One `isScreenReaderEnabled()`
- * query and one `screenReaderChanged` listener for the whole tree; every consumer reads
- * the resulting boolean from context instead of attaching its own listener per mount.
- *
- * Gated on the AccessibilityContext `enabled` flag: when the SDK's a11y is opted out, no
- * query is made and no listener is attached.
+ * Owns the app-wide screen reader subscription, so consumers read one boolean from context instead
+ * of each attaching a listener. Nothing is queried or subscribed while the SDK's a11y is disabled.
  */
 export const ScreenReaderProvider = ({ children }: PropsWithChildren) => {
   const { enabled: a11yEnabled } = useAccessibilityContext();
@@ -38,7 +34,7 @@ export const ScreenReaderProvider = ({ children }: PropsWithChildren) => {
         if (!cancelled) setScreenReaderEnabled(value);
       })
       .catch(() => {
-        // Some platforms / environments may not implement this; fall back to false.
+        // Some platforms do not implement this; stay at false.
       });
 
     const subscription = AccessibilityInfo.addEventListener(

package/src/contexts/swipeableContext/SwipeRegistryContext.tsx

@@ -38,6 +38,7 @@ export const SwipeRegistryProvider = ({ children }: PropsWithChildren) => {
       const registered = swipeablesRef.current?.get(id);
       if (registered === close) {
         swipeablesRef.current?.delete(id);
+        openRef.current?.delete(id);
       }
     };
   }, []);

package/src/contexts/themeContext/ThemeContext.tsx

@@ -20,11 +20,9 @@ export type DeepPartial<T> = {
  * A custom theme passed to `<Chat style={...}>` / `<ThemeProvider style={...}>`: either a partial
  * override tree or a complete `Theme`.
  *
- * `Theme` is listed first deliberately. A full `Theme` *is* structurally a valid `DeepPartial<Theme>`,
- * but from React Native 0.87 the style types underpinning `Theme` are deep enough that asking
- * TypeScript to prove it exceeds its instantiation depth limit (TS2589). Accepting `Theme` directly
- * means neither the SDK nor integrators need the `as DeepPartial<Theme>` cast that used to be
- * required, and the cheap branch is matched first.
+ * `Theme` is listed first because a full `Theme` is structurally a valid `DeepPartial<Theme>`, but
+ * with React Native 0.87 style types, proving that exceeds TypeScript's instantiation depth limit
+ * (TS2589). Matching `Theme` directly avoids the `as DeepPartial<Theme>` cast.
  */
 export type ThemeStyle = Theme | DeepPartial<Theme>;
 
@@ -91,7 +89,7 @@ export const useTheme = () => {
 
   if (theme === DEFAULT_BASE_CONTEXT_VALUE && !isTestEnvironment()) {
     throw new Error(
-      'The useThemeContext hook was called outside the ThemeContext Provider. Make sure you have configured OverlayProvider component correctly - https://getstream.io/chat/docs/sdk/reactnative/basics/hello_stream_chat/#overlay-provider',
+      'The useThemeContext hook was called outside the ThemeContext Provider. Make sure you have configured OverlayProvider component correctly - https://getstream.io/chat/docs/sdk/react-native/core-components/overlay-provider/',
     );
   }
   return { theme };