-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(602): fixing submission trend request #619
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review by PO - changes approved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks solid to me
|
||
// Generate the DTOs in the custom order | ||
return yearMonths.stream() | ||
.map(yearMonth -> new OpeningsPerYearDto( | ||
yearMonth.getMonthValue(), | ||
yearMonth.getYear(), | ||
getMonthName(yearMonth.getMonthValue()), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the month name can be omitted, either here or in future endpoints, it's something front end can do quite well
Description
Fixes an issue with the submission trends that happened during the aggregation phase, where the backend application was using all of the available resources to do the aggregation.
Fixes #602
Type of change
How Has This Been Tested?
Checklist
Further comments
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in:
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: