-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: adding aggregate operation #64
Conversation
64c9320
to
7ca7c96
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Code Climate has analyzed commit 2383a06 and detected 4 issues on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 98.8%. View more on Code Climate. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
a5a5e48
to
e6007a9
Compare
This operation is fast, but I'm not sure how useful it is and just an overkill. |
e6007a9
to
6d036ce
Compare
Quality Gate passedIssues Measures |
This operation has lost to branch:
Closing it |
The aggregation operation allows you to execute several aggregations in just one command.
Here is an example of use:
In the example, result will resolve to the following value:
Look that every distinct call for each aggregation method generates a distinct aggregation, so, you can use multiple times the same aggregation!
There are some limitations though: it's important that every call is always made in the same order, otherwise, this control will not work.
But let's say, for any reason, you can't follow this direction. In this case, you can indicate to the aggregation function an id to orientate it:
The example above will generate a result equal to (5 mod 3) + (6 mod 5) + ((5 + 9) mod 3), which is 5.
In general, is better to keep things simple to understand unless extremely necessary, as aggregations with such bifurcations can be quite hard to understand and to debug.