You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UI provides a number of functions that interact with the client while keeping the UI state in sync using `context`.
106
-
The [API Reference](<!-- TODO: Change to new docs -->) details what functions are accessible.
106
+
The [contexts section](../contexts/attachment_picker_context.mdx) details what functions are accessible.
107
107
When customizing your application you should ensure you are utilizing the correct functions to keep the UI state up to date.
108
108
109
109
The `sendMessage` function for instance, provided by `useMessageInputContext`, is not the same as the `sendMessage` function found directly on a `channel` in the client.
Copy file name to clipboardExpand all lines: docusaurus/docs/reactnative/basics/hello_stream_chat.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -404,7 +404,7 @@ But as a thread on a mobile messaging app generally exists in a separate screen
404
404
The simple code snippet can be extended to include `Thread` and keep track of a `thread` state similarly to `channel` by utilizing the `onThreadSelect` prop on the `MessageList`.
405
405
The code snippet now has a fully functional `ChannelList`, `MessageList`, and `threadList`, although currently it provides no way to *back* out of the sudo-navigation.
406
406
407
-
For additional information on the `Thread` component, such as how to use `onThreadDismount` to manage your `thread` state, check the [Thread component docs.](<!-- TODO: Change to new docs -->)
407
+
For additional information on the `Thread` component, such as how to use `onThreadDismount` to manage your `thread` state, check the [Thread component docs.](../ui-components/thread.mdx)
Copy file name to clipboardExpand all lines: docusaurus/docs/reactnative/basics/stream_chat_with_navigation.mdx
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,6 @@ title: Stream Chat with Navigation
7
7
importTabsfrom'@theme/Tabs';
8
8
importTabItemfrom'@theme/TabItem';
9
9
10
-
<!--TODO:Changetonewdocsforlinks-->
11
-
12
10
Stream Chat for React Native provides many features out of the box that require positioning on the screen in a certain manor to result in the desired UI.
13
11
The `AttachmentPicker`, `ImageGallery`, and `MessageOverlay`, all need to be rendered in front of other components to have the desired effect.
14
12
All of these elements are controlled by the `OverlayProvider`, when used together with navigation considerations need to be taken in how these will appear.
@@ -33,8 +31,6 @@ The [`NavigationContainer`](https://reactnavigation.org/docs/navigation-containe
33
31
Nested navigators and screens all exist within the container.
34
32
To ensure the `OverlayProvider` can render content above all of these screens, headers, tab-bars, etc. the `OverlayProvider` must be rendered around them.
35
33
36
-
<!--TODO:Changetonewdocsforlinks-->
37
-
38
34
[As noted in Hello Stream Chat](./hello_stream_chat.mdx#chat) the `Chat` component can either surround the entire application or be rendered locally on a screen.
39
35
You can choose whatever suits your needs best, theming, connection handling, and translations are all handled out of the box in the `Chat` component; and this may be a consideration in where in the app you want this component to be rendered.
40
36
@@ -43,7 +39,7 @@ You can choose whatever suits your needs best, theming, connection handling, and
43
39
Having it higher in the _stack_ helps to ensure it is not unmounted at times when a connection is present.
44
40
If `Chat` is unmounted with a connection present you may have to implement some connection handling functions yourself to ensure you reconnect when the app is, for instance, reopened from the background.
45
41
The WebSocket connection closes on it's own approximately 15 seconds after the app is backgrounded.
Not handling the connection on [`appState`](https://reactnative.dev/docs/appstate) changes will also effect [how Stream Chat handles Push Notifications](../guides/push_notifications.mdx).
0 commit comments