Skip to content

Commit c5039e4

Browse files
committed
remove old unneeded TODOs and fix some of our internal missing links
1 parent a187405 commit c5039e4

File tree

3 files changed

+3
-7
lines changed

3 files changed

+3
-7
lines changed

docusaurus/docs/reactnative/basics/client.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ const { client } = useChatContext();
103103
### Using UI Functions
104104

105105
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.
107107
When customizing your application you should ensure you are utilizing the correct functions to keep the UI state up to date.
108108

109109
The `sendMessage` function for instance, provided by `useMessageInputContext`, is not the same as the `sendMessage` function found directly on a `channel` in the client.

docusaurus/docs/reactnative/basics/hello_stream_chat.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -404,7 +404,7 @@ But as a thread on a mobile messaging app generally exists in a separate screen
404404
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`.
405405
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.
406406

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)
408408

409409
</div>
410410
<img src={thread} alt="Thread" width="280" style={{ objectFit: 'contain', paddingBottom: '8px', paddingLeft: '8px' }} />

docusaurus/docs/reactnative/basics/stream_chat_with_navigation.mdx

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,6 @@ title: Stream Chat with Navigation
77
import Tabs from '@theme/Tabs';
88
import TabItem from '@theme/TabItem';
99

10-
<!-- TODO: Change to new docs for links -->
11-
1210
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.
1311
The `AttachmentPicker`, `ImageGallery`, and `MessageOverlay`, all need to be rendered in front of other components to have the desired effect.
1412
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
3331
Nested navigators and screens all exist within the container.
3432
To ensure the `OverlayProvider` can render content above all of these screens, headers, tab-bars, etc. the `OverlayProvider` must be rendered around them.
3533

36-
<!-- TODO: Change to new docs for links -->
37-
3834
[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.
3935
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.
4036

@@ -43,7 +39,7 @@ You can choose whatever suits your needs best, theming, connection handling, and
4339
Having it higher in the _stack_ helps to ensure it is not unmounted at times when a connection is present.
4440
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.
4541
The WebSocket connection closes on it's own approximately 15 seconds after the app is backgrounded.
46-
Not handling the connection on [`appState`](https://reactnative.dev/docs/appstate) changes will also effect <!-- TODO: Change to new docs for links -->[how Stream Chat handles Push Notifications](https://getstream.io/chat/docs/react-native/push_introduction/?language=javascript).
42+
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).
4743

4844
:::
4945

0 commit comments

Comments
 (0)