pkoppstein

As of v1.1.4, the error message has vanished, so closing this issue.

@davidfetter - Some observations: a) there is no reason to define $in in the body of the def; b) for strings, `explode | reverse | implode` is much faster (approx...

@davidfetter - The trimmed down def has three bugs in it (e.g. it still assumes $in has been defined). Also, to avoid the second type check, I'd suggest: def reverse:...

An `aggregate_add/0` can be defined quite adequately in jq itself, e.g.: ``` def aggregate_add: reduce .[] as $o ({}; reduce ($o|keys[]) as $key (.; .[$key] += $o[$key])); ``` However, the...

@soerenwolfers asked: > do you have an example that doesn't use the CASE clause? I'm not sure the following will be helpful, but since you asked: ``` create or replace...

@soerenwolfers - Sorry for the noise. Any chance of turning this "Issue" into an enhancement request for the documentation to use a different font and/or color for the syntactic markers?

@szarnyasg wrote: > I took a look at this issue again There's nothing quite like simplicity :-) The one thing that's not immediately clear, though, is that both functions can...

Would it be feasible to support @dsv(delim), so that one could write, for example, @dsv(";")

Since `@SSV` is ambiguous (between space or semicolon) and `@DSV(delim)` presents implementation issues, the obvious choice is `@SCSV`. This is confirmed by ChatGPT's advice: ``` The most consistent and intuitive...

@01mf02 wrote: > all versions of jq can benefit from an up-to-date manual Do you mean going all the way back to v1.3? That would be an enormous amount of...