Ver Fonte

Inline docs: Use Twig's array literal rather than the split filter for sort_by

Daniel Rudolf há 8 anos atrás
pai
commit
cdba66b951
1 ficheiros alterados com 5 adições e 5 exclusões
  1. 5 5
      content-sample/index.md

+ 5 - 5
content-sample/index.md

@@ -227,12 +227,12 @@ Additional to Twigs extensive list of filters, functions and tags, Pico also
 provides some useful additional filters to make theming easier. You can parse
 any Markdown string to HTML using the `markdown` filter. Arrays can be sorted
 by one of its keys or a arbitrary deep sub-key using the `sort_by` filter
-(e.g. `{% for page in pages|sort_by("meta:nav"|split(":")) %}...{% endfor %}`
+(e.g. `{% for page in pages|sort_by([ 'meta', 'nav' ]) %}...{% endfor %}`
 iterates through all pages, ordered by the `nav` meta header; please note the
-`"meta:nav"|split(":")` part of the example, which passes `['meta', 'nav']` to
-the filter describing a key path). You can return all values of a given key or
-key path of an array using the `map` filter (e.g. `{{ pages|map("title") }}`
-returns all page titles).
+`[ 'meta', 'nav' ]` part of the example, it instructs Pico to sort by
+`page.meta.nav`). You can return all values of a given key or key path of an
+array using the `map` filter (e.g. `{{ pages|map("title") }}` returns all
+page titles).
 
 You can use different templates for different content files by specifying the
 `Template` meta header. Simply add e.g. `Template: blog-post` to a content file