From ca7280ac6638dab66171ddcfd7e945ca6d1f6408 Mon Sep 17 00:00:00 2001 From: Simon Shutter Date: Sun, 25 Feb 2024 15:57:00 -0800 Subject: [PATCH 1/3] Update 10-routing.md Added a note about the dependency of +layout.svelte on +layout.ts. --- documentation/docs/20-core-concepts/10-routing.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/documentation/docs/20-core-concepts/10-routing.md b/documentation/docs/20-core-concepts/10-routing.md index d21be05291af..74a09a863b59 100644 --- a/documentation/docs/20-core-concepts/10-routing.md +++ b/documentation/docs/20-core-concepts/10-routing.md @@ -205,6 +205,8 @@ We can create a layout that only applies to pages below `/settings` (while inher ``` +Note that if you want to leverage an `#each` block to dynamically build the nav menu in the code above, you will need to define the _sections_ array. See `+layout.js` below for the matching example. + By default, each layout inherits the layout above it. Sometimes that isn't what you want - in this case, [advanced layouts](advanced-routing#advanced-layouts) can help you. ### +layout.js From f3ddf1d22e763611447e716b2e3a513f23a8b6e1 Mon Sep 17 00:00:00 2001 From: Simon Shutter Date: Mon, 26 Feb 2024 08:12:03 -0800 Subject: [PATCH 2/3] Update documentation/docs/20-core-concepts/10-routing.md Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com> --- documentation/docs/20-core-concepts/10-routing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/20-core-concepts/10-routing.md b/documentation/docs/20-core-concepts/10-routing.md index 74a09a863b59..680d54adce4e 100644 --- a/documentation/docs/20-core-concepts/10-routing.md +++ b/documentation/docs/20-core-concepts/10-routing.md @@ -205,7 +205,7 @@ We can create a layout that only applies to pages below `/settings` (while inher ``` -Note that if you want to leverage an `#each` block to dynamically build the nav menu in the code above, you will need to define the _sections_ array. See `+layout.js` below for the matching example. +You can see how `data` is populated in the `+layout.js` example in the next section just below. By default, each layout inherits the layout above it. Sometimes that isn't what you want - in this case, [advanced layouts](advanced-routing#advanced-layouts) can help you. From f9f9e48b9597efbe182731c9921b48cd8adf8ceb Mon Sep 17 00:00:00 2001 From: Ben McCann <322311+benmccann@users.noreply.github.com> Date: Mon, 26 Feb 2024 10:31:32 -0800 Subject: [PATCH 3/3] Update documentation/docs/20-core-concepts/10-routing.md --- documentation/docs/20-core-concepts/10-routing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/20-core-concepts/10-routing.md b/documentation/docs/20-core-concepts/10-routing.md index 680d54adce4e..66f9ce3a6091 100644 --- a/documentation/docs/20-core-concepts/10-routing.md +++ b/documentation/docs/20-core-concepts/10-routing.md @@ -205,7 +205,7 @@ We can create a layout that only applies to pages below `/settings` (while inher ``` -You can see how `data` is populated in the `+layout.js` example in the next section just below. +You can see how `data` is populated by looking at the `+layout.js` example in the next section just below. By default, each layout inherits the layout above it. Sometimes that isn't what you want - in this case, [advanced layouts](advanced-routing#advanced-layouts) can help you.