From a89650a7fa18e39204fbcfa3ba382b75b7188d3c Mon Sep 17 00:00:00 2001
From: Thomas Gassmann <thomas.gassmann@hotmail.com>
Date: Thu, 24 Oct 2019 22:05:21 +0200
Subject: [PATCH] =?UTF-8?q?Close=20missing=20suspense=20tags=20in=20docume?=
=?UTF-8?q?ntation=20for=20concurrent=20UI=E2=80=A6=20(#2475)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
content/docs/concurrent-mode-patterns.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/content/docs/concurrent-mode-patterns.md b/content/docs/concurrent-mode-patterns.md
index c36bb3f0..2f4e4996 100644
--- a/content/docs/concurrent-mode-patterns.md
+++ b/content/docs/concurrent-mode-patterns.md
@@ -390,6 +390,7 @@ After the click, React started rendering the next screen:
<ProfileDetails />
<Suspense fallback={...}>
<ProfileTimeline />
+ </Suspense>
</ProfilePage>
</Suspense>
```
@@ -403,6 +404,7 @@ Both `<ProfileDetails>` and `<ProfileTimeline>` need data to render, so they sus
<ProfileDetails /> {/* suspends! */}
<Suspense fallback={<h2>Loading posts...</h2>}>
<ProfileTimeline /> {/* suspends! */}
+ </Suspense>
</ProfilePage>
</Suspense>
```
@@ -419,6 +421,7 @@ When a component suspends, React needs to show the closest fallback. But the clo
<ProfileDetails /> {/* suspends! */}
<Suspense fallback={...}>
<ProfileTimeline />
+ </Suspense>
</ProfilePage>
</Suspense>
```
@@ -437,6 +440,7 @@ As we load more data, React will retry rendering, and `<ProfileDetails>` can ren
<h2>Loading posts...</h2>
}>
<ProfileTimeline /> {/* suspends! */}
+ </Suspense>
</ProfilePage>
</Suspense>
```