Add orderBy, first and last parameters to groupedAggregates #80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
More context on #75. Closes #75
Basically adds
orderBy,firstandlastparameters togroupedAggregates.orderByaccepts any possible field aggregations. Note that I still don't have a very good understanding of the project, this PR is party AI generated and partly from copy pasting various concepts around, would appreciate deep review from someone who understands the code better to see if there can better ways.Performance impact
Slight performance impact in startup time due to added(18 entries per numerical fields in AggregatesOrderBy enum)
Security impact
Shouldn't be.
Checklist
yarn lint:fixpasses. - I'm working on estlint to run properlyyarn testpasses.RELEASE_NOTES.mdfile (if one exists). - File doesn't exist