Browse Source

Close missing suspense tags in documentation for concurrent UI… (#2475)

main
Thomas Gassmann 5 years ago
committed by Alexey Pyltsyn
parent
commit
a89650a7fa
  1. 4
      content/docs/concurrent-mode-patterns.md

4
content/docs/concurrent-mode-patterns.md

@ -390,6 +390,7 @@ After the click, React started rendering the next screen:
<ProfileDetails /> <ProfileDetails />
<Suspense fallback={...}> <Suspense fallback={...}>
<ProfileTimeline /> <ProfileTimeline />
</Suspense>
</ProfilePage> </ProfilePage>
</Suspense> </Suspense>
``` ```
@ -403,6 +404,7 @@ Both `<ProfileDetails>` and `<ProfileTimeline>` need data to render, so they sus
<ProfileDetails /> {/* suspends! */} <ProfileDetails /> {/* suspends! */}
<Suspense fallback={<h2>Loading posts...</h2>}> <Suspense fallback={<h2>Loading posts...</h2>}>
<ProfileTimeline /> {/* suspends! */} <ProfileTimeline /> {/* suspends! */}
</Suspense>
</ProfilePage> </ProfilePage>
</Suspense> </Suspense>
``` ```
@ -419,6 +421,7 @@ When a component suspends, React needs to show the closest fallback. But the clo
<ProfileDetails /> {/* suspends! */} <ProfileDetails /> {/* suspends! */}
<Suspense fallback={...}> <Suspense fallback={...}>
<ProfileTimeline /> <ProfileTimeline />
</Suspense>
</ProfilePage> </ProfilePage>
</Suspense> </Suspense>
``` ```
@ -437,6 +440,7 @@ As we load more data, React will retry rendering, and `<ProfileDetails>` can ren
<h2>Loading posts...</h2> <h2>Loading posts...</h2>
}> }>
<ProfileTimeline /> {/* suspends! */} <ProfileTimeline /> {/* suspends! */}
</Suspense>
</ProfilePage> </ProfilePage>
</Suspense> </Suspense>
``` ```

Loading…
Cancel
Save