Problem:
In some cases, when the number of participants is big, we were needlessly calculating getDisplayNameForParticipant where in the end, we wouldn't be able to display it since the output is trimmed afterwards anyways.
Solution
The number of participants used to determine the Report name via getReportName is limited to first 5 participants other than current user.
This change allows to cap the performance impact of getReportName (which is used within getOrderedReportIDs)
from here: https://expensify.slack.com/archives/C05LX9D6E07/p1709831181822099
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~01bcaa1758a6b23688
- Upwork Job ID: 1766057020696662016
- Last Price Increase: 2024-03-08
Problem:
In some cases, when the number of participants is big, we were needlessly calculating getDisplayNameForParticipant where in the end, we wouldn't be able to display it since the output is trimmed afterwards anyways.
Solution
The number of participants used to determine the Report name via getReportName is limited to first 5 participants other than current user.
This change allows to cap the performance impact of getReportName (which is used within getOrderedReportIDs)
from here: https://expensify.slack.com/archives/C05LX9D6E07/p1709831181822099
Upwork Automation - Do Not Edit