Issue #191 fixes both $..allTheThings.max() and $.max($..allTheThings)

[mgreenwood1001]

Issue #191 is an unintentional side-effect of the collection processing for parameters passed to functions. This change supports result set functions via patterns such as:

$.max($..allTheNumberThings)

$.max($.foo, $.bar) is already supported where foo and bar are numbers - consequently

$.max($..allTheNumberThings) shall also work also

$.avg($..allTheNumberThings, $.someCollection.max(), $..someOtherNumberThings)
will work too now with this change.

[mgreenwood1001]

IntelliJ was having a bad day I guess, its in the same package, ugh - I'll fix this...

[mgreenwood1001]

the original question raised by #191 wanted to use the notation:

$..pathWithResultSetOutput.function()

so I've added support for that as well.

Normally, this won't work unless you make the graph stateful or introduce a pre-aggregation function (or emulate this in the evaluation steps) -- aggregate the results as a collection and passes it along to the function, i.e. $..path.group().min() -- I'm not fond of this approach.

Instead, The CompilePath function now recognizes the condition where you're scanning the elements and introducing a collection as a the result set and attempting to pass that along as input into the function, since that won't work (functions are stateless and require parameters that can be lazy evaluated or passed) the CompilePath now inverts the graph making the function the root token and the parameter to the function the original path which makes the whole thing sane such that we can lazy evaluate the path get the result then evaluate the function.

So now:

$..path.sum() and

$.sum($..path) are supported, it won't matter which you specify as both result in the same graph internally.

Since this CompilePath trick is in the constructor, its recursive, so

$.sum($..path.sum(), $..path.avg())

do what you'd hope it would do...

[rhavermans]

@kallestenflo Could you make a new release? We would like to have this functionality.

[soberich]

@mgreenwood1001 @kallestenflo Hey, guys, I just stumbled upon fact that this is really weird.. Why is it that many useful commits are on master but the artifact is still not released (for more than a year)? Anyone?

[mgreenwood1001]

@kallestenflo should you need anything from me for a release please let me know.

[soberich]

I've made pr with div() and mult() functions #511.
It's a master branch fork. So, would be nice to merge all that.

[sarod]

@kallestenflo @mgreenwood1001 this feature would be really useful. It was merged in a year and a half ago. Is there a release planned soon?

[aabrams]

+1 Really useful to have this released, thanks!

[ericnesschrw]

This would be really useful. Any plans to release it?