mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-14 20:37:55 -05:00
d3927310d5
1798dc0d5 Update theme 403fa716e Update CLI documentation (#2092) aade5a09e Correct media subtype example 53cd9dea6 netlify: Hugo 0.112.3 b78b86cb1 Add source/target warning to resources.Copy (#2091) 50c299729 netlify: Hugo 0.112.2 73197046f Change config.xxx to hugo.xxx throughout the documentation (#2090) d489d4c6f Add hugo.WorkingDir to docs (#2089) 7487df809 Fix typos (#2088) 6d0572cd6 netlify: Hugo 0.112.1 6838600b2 netlify: Hugo 0.112.0 513e7a80f Merge branch 'tempv0.112.0' 91eb44275 Some more about 0.112.0 bd3b33a27 docs: Regen docshelper fb3027daf docs: Regen CLI docs 8e7b8e987 Merge commit 'f96384a3b596f9bc0a3a035970b09b2c601f0ccb' a942ceef4 tpl/tplimpl: Add img loading attribute to figure shortcode (#10927) 0e0c7b25e tpl/urls: Return empty string when JoinPath has zero args 310ce949a tpl/urls: Add JoinPath template function ae435ca77 tpl: Add math.Abs f340139f8 Revert "Update syntax-highlighting.md (#10929)" (#10930) 917a0e24d Update syntax-highlighting.md (#10929) git-subtree-dir: docs git-subtree-split: 1798dc0d54ce048dd975863b490cd809ef14268a
167 lines
5 KiB
Markdown
167 lines
5 KiB
Markdown
---
|
|
title: where
|
|
description: Filters an array to only the elements containing a matching value for a given field.
|
|
categories: [functions]
|
|
menu:
|
|
docs:
|
|
parent: functions
|
|
keywords: [filtering]
|
|
signature: ["where COLLECTION KEY [OPERATOR] MATCH"]
|
|
relatedfuncs: [intersect,first,after,last]
|
|
toc: true
|
|
---
|
|
|
|
`where` filters an array to only the elements containing a matching
|
|
value for a given field.
|
|
|
|
It works in a similar manner to the [`where` keyword in
|
|
SQL][wherekeyword].
|
|
|
|
```go-html-template
|
|
{{ range where .Pages "Section" "foo" }}
|
|
{{ .Content }}
|
|
{{ end }}
|
|
```
|
|
|
|
It can be used by dot-chaining the second argument to refer to a nested element of a value.
|
|
|
|
{{< code-toggle file="content/example.md" fm=true copy=false >}}
|
|
title: Example
|
|
series: golang
|
|
{{< /code-toggle >}}
|
|
|
|
```go-html-template
|
|
{{ range where .Site.Pages "Params.series" "golang" }}
|
|
{{ .Content }}
|
|
{{ end }}
|
|
```
|
|
|
|
It can also be used with the logical operators `!=`, `>=`, `in`, etc. Without an operator, `where` compares a given field with a matching value equivalent to `=`.
|
|
|
|
```go-html-template
|
|
{{ range where .Pages "Section" "!=" "foo" }}
|
|
{{ .Content }}
|
|
{{ end }}
|
|
```
|
|
|
|
The following logical operators are available with `where`:
|
|
|
|
`=`, `==`, `eq`
|
|
: `true` if a given field value equals a matching value
|
|
|
|
`!=`, `<>`, `ne`
|
|
: `true` if a given field value doesn't equal a matching value
|
|
|
|
`>=`, `ge`
|
|
: `true` if a given field value is greater than or equal to a matching value
|
|
|
|
`>`, `gt`
|
|
: `true` if a given field value is greater than a matching value
|
|
|
|
`<=`, `le`
|
|
: `true` if a given field value is lesser than or equal to a matching value
|
|
|
|
`<`, `lt`
|
|
: `true` if a given field value is lesser than a matching value
|
|
|
|
`in`
|
|
: `true` if a given field value is included in a matching value; a matching value must be an array or a slice
|
|
|
|
`not in`
|
|
: `true` if a given field value isn't included in a matching value; a matching value must be an array or a slice
|
|
|
|
`intersect`
|
|
: `true` if a given field value that is a slice/array of strings or integers contains elements in common with the matching value; it follows the same rules as the [`intersect` function][intersect].
|
|
|
|
## Use `where` with `Booleans`
|
|
When using booleans you should not put quotation marks.
|
|
```go-html-template
|
|
{{ range where .Pages "Draft" true }}
|
|
<p>{{ .Title }}</p>
|
|
{{ end }}
|
|
```
|
|
|
|
|
|
## Use `where` with `intersect`
|
|
|
|
```go-html-template
|
|
{{ range where .Site.Pages "Params.tags" "intersect" .Params.tags }}
|
|
{{ if ne .Permalink $.Permalink }}
|
|
{{ .Render "summary" }}
|
|
{{ end }}
|
|
{{ end }}
|
|
```
|
|
|
|
You can also put the returned value of the `where` clauses into a variable:
|
|
|
|
{{< code file="where-intersect-variables.html" >}}
|
|
{{ $v1 := where .Site.Pages "Params.a" "v1" }}
|
|
{{ $v2 := where .Site.Pages "Params.b" "v2" }}
|
|
{{ $filtered := $v1 | intersect $v2 }}
|
|
{{ range $filtered }}
|
|
{{ end }}
|
|
{{< /code >}}
|
|
|
|
## Use `where` with `first`
|
|
|
|
Using `first` and `where` together can be very
|
|
powerful. Below snippet gets a list of posts only from [**main
|
|
sections**](#mainsections), sorts it using the [default
|
|
ordering](/templates/lists/) for lists (i.e., `weight => date`), and
|
|
then ranges through only the first 5 posts in that list:
|
|
|
|
{{< code file="first-and-where-together.html" >}}
|
|
{{ range first 5 (where site.RegularPages "Type" "in" site.Params.mainSections) }}
|
|
{{ .Content }}
|
|
{{ end }}
|
|
{{< /code >}}
|
|
|
|
## Nest `where` Clauses
|
|
|
|
You can also nest `where` clauses to drill down on lists of content by more than one parameter. The following first grabs all pages in the "blog" section and then ranges through the result of the first `where` clause and finds all pages that are *not* featured:
|
|
|
|
```go-html-template
|
|
{{ range where (where .Pages "Section" "blog" ) "Params.featured" "!=" true }}
|
|
```
|
|
|
|
## Unset Fields
|
|
|
|
Filtering only works for set fields. To check whether a field is set or exists, you can use the operand `nil`.
|
|
|
|
This can be useful to filter a small amount of pages from a large pool. Instead of setting a field on all pages, you can set that field on required pages only.
|
|
|
|
Only the following operators are available for `nil`
|
|
|
|
* `=`, `==`, `eq`: True if the given field is not set.
|
|
* `!=`, `<>`, `ne`: True if the given field is set.
|
|
|
|
```go-html-template
|
|
{{ range where .Pages "Params.specialpost" "!=" nil }}
|
|
{{ .Content }}
|
|
{{ end }}
|
|
```
|
|
|
|
## Portable `where` filters -- `site.Params.mainSections` {#mainsections}
|
|
|
|
**This is especially important for themes.**
|
|
|
|
To list the most relevant pages on the front page or similar, you
|
|
should use the `site.Params.mainSections` list instead of comparing
|
|
section names to hard-coded values like `"posts"` or `"post"`.
|
|
|
|
```go-html-template
|
|
{{ $pages := where site.RegularPages "Type" "in" site.Params.mainSections }}
|
|
```
|
|
|
|
If the user has not set this config parameter in their site config, it
|
|
will default to the *section with the most pages*.
|
|
|
|
The user can override the default:
|
|
|
|
{{< code-toggle file="hugo" >}}
|
|
[params]
|
|
mainSections = ["blog", "docs"]
|
|
{{< /code-toggle >}}
|
|
|
|
[intersect]: /functions/intersect/
|
|
[wherekeyword]: https://www.techonthenet.com/sql/where.php
|