L3 - Default AT:
- the duplicated code in GroupByCandidateGroup and GroupByAssignee classes is merged
- the command sorting functionality is moved to the CompositeCommandResult class
- the duplicated code in ProcessGroupByVariable and AbstractDecisionGroupByVariable is merged
- the GroupByDateVariableIntervalSelection utility class is being removed as well
Context:
To make the refactoring easier parts of the code have been duplicated. Since this ticket represents the clean up, the code duplication should now be merged.
Sebastian Bathke:
as the CompositeCommandResult is created by the groupByPart.retrieveQueryResult already do you think it would make sense to forward that information (numeric or not) from there into the composite result so it could be picked up from there as an property of the CompositeCommandResult?
actually couldn't the sorting already be done completely inside retrieveQueryResult on the CompositeCommandResult? as all the stuff related to sorting originates from the groupByPart anyway and then the ReportResultDto doesn't even need sorting functionality it will be just a plain POJO?