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
Copy file name to clipboardExpand all lines: website/docs/13.x/docs/guides/react-19.mdx
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ React 19 introduced full support for React Suspense, `React.use()`, and other as
6
6
7
7
React 19's async rendering features make React's rendering process more asynchronous by nature. This requires the use of the [`async act`](https://react.dev/reference/react/act) helper when testing components that use these new APIs, which in turn affects several React Native Testing Library APIs.
8
8
9
-
Note that `renderAsync`, and other changes support React 18.
9
+
Note that `renderAsync` and other async APIs also support React 18.
10
10
11
11
## New Async APIs in RNTL 13.3
12
12
@@ -23,8 +23,8 @@ To support React 19's async rendering, RNTL 13.3 introduces several new async AP
23
23
Some APIs didn't require changes:
24
24
25
25
-`screen` object: most of the methods, including queries
26
-
-**[`userEvent`](docs/api/user-event) didn't require API changes as it was already async
27
-
- Jest Matchers didn't require any changes as they work already processed output
26
+
-**[`userEvent`](docs/api/user-event)** didn't require API changes as it was already async
27
+
-**Jest Matchers** didn't require any changes as they work with already processed output
28
28
29
29
## Key Changes for Testing
30
30
@@ -53,4 +53,4 @@ While these async APIs are new in RNTL 13.3, we expect them to become the defaul
53
53
-**New testing code**: use the async APIs (`renderAsync`, etc.) for all new tests
54
54
-**Legacy testing code**: can continue using the synchronous versions (`render`, etc.) without any required changes
55
55
56
-
This approach allows for gradual migration while ensuring compatibility with both React 18 and React 19 features.
56
+
This approach allows for gradual migration while ensuring compatibility with both React 18 and React 19 features.
0 commit comments