Skip to content

[HOLD for payment 2023-12-18] [$500] ReportUtils.shouldReportBeInOptionList will always be falsy for specific reports #30842

@kubabutkiewicz

Description

@kubabutkiewicz

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


During Typescript migration I noticed that in SidebarUtils module in getOrderedReportIDs function we have allReportActions param which is typed as Record<string, ReportAction[]>. It's used in ReportUtils.shouldReportBeInOptionList function. If we go deeper inside ReportUtils.shouldReportBeInOptionList it will be used in ReportUtils.canAccessReport then there it will be used in ReportActionsUtils.getParentReportAction which expects that allReportActions will be a collection of object no collection of arrays, which could lead into problems. There is no bug which I noticed yet, but I think its worth of checking.

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

image image

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01e1c89ccf309fa85a
  • Upwork Job ID: 1721662000620908544
  • Last Price Increase: 2023-11-27

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions