From fc960c1771d8b49c9eee9a265cabee8efc710421 Mon Sep 17 00:00:00 2001 From: Vincent Prouillet Date: Mon, 1 May 2017 17:31:51 +0900 Subject: [PATCH] Do not populate prev/next on section index rendering --- README.md | 2 +- src/site.rs | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2bc08e1e..0df38ae3 100644 --- a/README.md +++ b/README.md @@ -106,7 +106,7 @@ along with it that are NOT markdown. Those assets will be copied in the same folder when building so you can just use a relative path to use them. A summary is only defined if you put `` in the content. If present in a page, the summary will be from -the start up to that tag.s +the start up to that tag. ### Sections Sections represent a group of pages, for example a `tutorials` section of your site. diff --git a/src/site.rs b/src/site.rs index c86fa815..e9069390 100644 --- a/src/site.rs +++ b/src/site.rs @@ -202,7 +202,7 @@ impl Site { for (parent_path, section) in &mut self.sections { // TODO: avoid this clone let (sorted_pages, _) = sort_pages(section.pages.clone(), Some(§ion)); - section.pages = populate_previous_and_next_pages(sorted_pages.as_slice()); + section.pages = sorted_pages; match grandparent_paths.get(parent_path) { Some(paths) => section.subsections.extend(paths.clone()),