From a53f9a704dd269d718c9d2379b506b358a344045 Mon Sep 17 00:00:00 2001 From: GOWTHAM V BHAT Date: Thu, 30 Jun 2022 20:40:13 +0530 Subject: [PATCH] docs: Fix element tree structure for layout route example (#9025) * docs: Fix element tree structure * Update docs/getting-started/concepts.md Co-authored-by: Tim Dorr --- contributors.yml | 1 + docs/getting-started/concepts.md | 8 +++----- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/contributors.yml b/contributors.yml index acc98e192d..1bbe913333 100644 --- a/contributors.yml +++ b/contributors.yml @@ -70,3 +70,4 @@ - vijaypushkin - vikingviolinist - xcsnowcity +- gowthamvbhat diff --git a/docs/getting-started/concepts.md b/docs/getting-started/concepts.md index 450b537753..d1a5ce1837 100644 --- a/docs/getting-started/concepts.md +++ b/docs/getting-started/concepts.md @@ -657,11 +657,9 @@ Here's a part of our route config we haven't matched yet: `/privacy`. Let's look And the resulting element tree rendered will be: ```jsx - - - - - + + + ``` The `PageLayout` route is admittedly weird. We call it a [layout route](#layout-route) because it doesn't participate in the matching at all (though its children do). It only exists to make wrapping multiple child routes in the same layout simpler. If we didn't allow this then you'd have to handle layouts in two different ways: sometimes your routes do it for you, sometimes you do it manually with lots of layout component repetition throughout your app: