[CORRUPTED] Synthetic Benchmark PR #76098 - [CP Staging] revert: feat: [CFI] Add group-by report layout feature

[tomerqodo]

User description

Benchmark PR Expensify#76098

Type: Corrupted (contains bugs)

Original PR Title: [CP Staging] revert: feat: [CFI] Add group-by report layout feature
Original PR Description:

Explanation of Change

Revert of Expensify#72943

Fixed Issues

$ Expensify#76075
$ Expensify#76077
$ Expensify#76078
$ Expensify#76079
$ Expensify#76082
$ Expensify#76084
$ Expensify#76085
$ Expensify#76087
$ Expensify#76089
$ Expensify#76091
$ Expensify#76093

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

**Original PR URL**: https://github.com/Expensify/pull/76098

---

PR Type

Bug fix

---

Description

• Reverts group-by report layout feature completely

• Removes report layout constants, routes, and screens

• Deletes grouping utilities and transaction list modifications

• Removes localization strings across 10 languages

---

Diagram Walkthrough

flowchart LR
  A["Group-by Layout Feature"] -->|Revert| B["Feature Removed"]
  B --> C["Constants Deleted"]
  B --> D["Routes Removed"]
  B --> E["UI Components Deleted"]
  B --> F["Localization Cleaned"]

Loading

File Walkthrough

	Relevant files
Configuration changes	7 files index.ts Remove report layout group-by constants                                    +0/-6      ONYXKEYS.ts Remove NVP report layout group-by key                                        +0/-4      ROUTES.ts Remove report layout settings route                                            +0/-4      SCREENS.ts Remove report layout screen definition                                      +0/-1      config.ts Remove report layout navigation config                                      +0/-3      types.ts Remove report layout navigator param type                                +0/-3      index.tsx Remove report layout modal stack navigator                              +0/-1
Documentation	10 files de.ts Remove German report layout translations                                  +0/-12    en.ts Remove English report layout translations                                +0/-12    es.ts Remove Spanish report layout translations                                +0/-12    fr.ts Remove French report layout translations                                  +0/-12    it.ts Remove Italian report layout translations                                +0/-12    ja.ts Remove Japanese report layout translations                              +0/-12    nl.ts Remove Dutch report layout translations                                    +0/-12    pl.ts Remove Polish report layout translations                                  +0/-12    pt-BR.ts Remove Portuguese report layout translations                          +0/-12    zh-hans.ts Remove Chinese report layout translations                                +0/-12
Bug fix	8 files ReportLayoutUtils.ts Delete report layout grouping utilities                                    +0/-120  ReportSecondaryActionUtils.ts Remove report layout action check function                              +2/-17    ReportLayout.ts Delete report layout action handlers                                          +0/-51    ReportLayout.ts Delete report layout type definitions                                        +0/-26    index.ts Remove report layout type exports                                                +0/-3      MoneyRequestReportGroupHeader.tsx Delete group header component                                                        +0/-90    MoneyRequestReportTransactionList.tsx Remove grouping logic and group header rendering                  +21/-104 ReportLayoutPage.tsx Delete report layout settings page                                              +0/-82
Formatting	1 files index.ts Remove report layout group header styles                                  +0/-8

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Missing Auditing: The PR modifies secondary actions visibility (adding a length check to show report layout) without adding or referencing any audit logging of this critical UI action decision, but it’s unclear if logging is handled elsewhere. Referred Code if (reportTransactions.length >= 2) { options.push(CONST.REPORT.SECONDARY_ACTIONS.REPORT_LAYOUT); } Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Complete the feature revert properly The revert of the "group-by report layout" feature is incomplete. To prevent a crash, remove the code in src/libs/ReportSecondaryActionUtils.ts that still adds the "Report Layout" button to the secondary actions menu, as its corresponding screen has been deleted. Examples: src/libs/ReportSecondaryActionUtils.ts [691-693] if (reportTransactions.length >= 2) { options.push(CONST.REPORT.SECONDARY_ACTIONS.REPORT_LAYOUT); } Solution Walkthrough: Before: // src/libs/ReportSecondaryActionUtils.ts function getSecondaryReportActions(...) { const options = []; // ... other actions if (reportTransactions.length >= 2) { options.push(CONST.REPORT.SECONDARY_ACTIONS.REPORT_LAYOUT); } options.push(CONST.REPORT.SECONDARY_ACTIONS.DOWNLOAD_PDF); // ... return options; } After: // src/libs/ReportSecondaryActionUtils.ts function getSecondaryReportActions(...) { const options = []; // ... other actions // The "REPORT_LAYOUT" option is no longer added. options.push(CONST.REPORT.SECONDARY_ACTIONS.DOWNLOAD_PDF); // ... return options; } Suggestion importance[1-10]: 10 __ Why: This suggestion correctly identifies a critical bug where an incomplete feature revert leaves a UI element that will cause a crash, making it a high-impact and essential fix.	High
More