diff options
Diffstat (limited to 'docs/content/manual/v1.4/manual.yml')
-rw-r--r-- | docs/content/manual/v1.4/manual.yml | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/content/manual/v1.4/manual.yml b/docs/content/manual/v1.4/manual.yml index 22d10caa..a8923e11 100644 --- a/docs/content/manual/v1.4/manual.yml +++ b/docs/content/manual/v1.4/manual.yml @@ -957,7 +957,7 @@ sections: The `unique_by(.foo)` function takes as input an array and produces an array of the same elements, in sorted order, with - elqements with a duplicate `.foo` field removed. Think of it as making + elements with a duplicate `.foo` field removed. Think of it as making an array by taking one element out of every group produced by `group_by`. @@ -1290,8 +1290,8 @@ sections: The expression 'a == b' will produce 'true' if the result of a and b are equal (that is, if they represent equivalent JSON documents) and 'false' otherwise. In particular, strings are never considered equal - to numbers. If you're coming from Javascript, jq's == is like - Javascript's === - considering values equal only when they have the + to numbers. If you're coming from JavaScript, jq's == is like + JavaScript's === - considering values equal only when they have the same type as well as the same value. != is "not equal", and 'a != b' returns the opposite value of 'a == b' @@ -1308,7 +1308,7 @@ sections: as `C` otherwise. Checking for false or null is a simpler notion of - "truthiness" than is found in Javascript or Python, but it + "truthiness" than is found in JavaScript or Python, but it means that you'll sometimes have to be more explicit about the condition you want: you can't test whether, e.g. a string is empty using `if .name then A else B end`, you'll @@ -1571,7 +1571,7 @@ sections: If an object has two fields which are arrays, `.foo` and `.bar`, and you append something to `.foo`, then `.bar` will not get bigger. Even if you've just set `.bar = .foo`. If you're used to - programming in languages like Python, Java, Ruby, Javascript, + programming in languages like Python, Java, Ruby, JavaScript, etc. then you can think of it as though jq does a full deep copy of every object before it does the assignment (for performance, it doesn't actually do that, but that's the general idea). @@ -1588,7 +1588,7 @@ sections: .foo = .bar | .foo.baz = 1 will not have the side-effect of setting .bar.baz to be set - to 1, as the similar-looking program in Javascript, Python, + to 1, as the similar-looking program in JavaScript, Python, Ruby or other languages would. Unlike these languages (but like Haskell and some other functional languages), there is no notion of two arrays or objects being "the same array" or |