[Due for payment 2025-09-26] Remove call to `getReportNameValuePairs()` in method `getReportNameInternal` from `ReportUtils.ts`

[tgolen]

This is part of #59961 and will ensure that the function is a pure function.

No proposals are necessary for this.

Issue Owner

Current Issue Owner: @johncschuster

[melvin-bot]

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[Tony-MK]

@tgolen, could I work on this one?

[DylanDylann]

🔔 Note for Contributors: Please ensure that you are responsible in the PR phase to try to get it done soon

The function getReportNameInternal() is not a pure function because it references the report's NVPs from a global variable here. This is considered an anti-pattern that we are actively working to eliminate.

✅ Your Task

1. Verify that a unit test exists for getReportNameInternal() in its current form. If it doesn't, create one — and aim for high-quality, thorough coverage.

2. Refactor getReportNameInternal() into a pure function, and introduce a new parameter: isReportArchived = false (It is recommended to use useReportIsArchived to get isReportArchived). And update all instances in the codebase where getReportNameInternal() is called to accommodate the new isReportArchived parameter.

⚠️ Best Practices to Follow

1. Avoid adding new global references to data via Onyx.connect.
2. Avoid using isArchivedReport(nameValuePairs) unless absolutely necessary.
3. Prefer fetching data in a UI component, then pass it down via parameters.
4. Consider using the useReportIsArchived() React hook — it’s designed for this.
5. Before making changes, check if the report's NVPs are already available or if isReportArchived is already calculated or passed.

[DylanDylann]

@Tony-MK please read the above guideline. This may be a big change, let us know if you are able to be responsive and prioritise it.

[Tony-MK]

@Tony-MK please read the above guideline. This may be a big change, let us know if you are able to be responsive and prioritise it.

@DylanDylann, Sure, but does it still need a proposal?