Improve wording around all and any (#6524)

* Improve wording around `all` and `any`

The role of the `predicate` for `all` and `any` was not as clear.

See #6499

* type-o

* type-o

Co-authored-by: Darren Schroeder <343840+fdncred@users.noreply.github.com>
This commit is contained in:
Stefan Holderbach 2022-09-08 15:45:01 +02:00 committed by GitHub
parent d1e1d0ac3e
commit 1adebefc3e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 6 deletions

View File

@ -18,17 +18,17 @@ impl Command for All {
.required(
"predicate",
SyntaxShape::RowCondition,
"the predicate that must match",
"the predicate expression that must evaluate to a boolean",
)
.category(Category::Filters)
}
fn usage(&self) -> &str {
"Test if every element of the input matches a predicate."
"Test if every element of the input fulfills a predicate expression."
}
fn search_terms(&self) -> Vec<&str> {
vec!["every"]
vec!["every", "and"]
}
fn examples(&self) -> Vec<Example> {

View File

@ -18,17 +18,17 @@ impl Command for Any {
.required(
"predicate",
SyntaxShape::RowCondition,
"the predicate that must match",
"the predicate expression that should return a boolean",
)
.category(Category::Filters)
}
fn usage(&self) -> &str {
"Tests if any element of the input matches a predicate."
"Tests if any element of the input fulfills a predicate expression."
}
fn search_terms(&self) -> Vec<&str> {
vec!["some"]
vec!["some", "or"]
}
fn examples(&self) -> Vec<Example> {