(1/2) Add support for all reportAction types in ChatListItem - create PureReportActionItem

[wildan-m]

Explanation of Change

Initial PR for adding support for all reportAction types in ChatListItem. Extracted onyx data to params to create PureReportAction component.

Fixed Issues

$ #51296
PROPOSAL: #51296 (comment)

Tests

No specific test required, just ensure that the report action item functions correctly as usual.
Ensure these actions works as usual:

• commenting
• sending expenses,
• creating tasks
• add emoji
• reply thread
• mark as unread
• deleting comment
• Verify that no errors appear in the JS console

Offline tests

Same as Test

QA Steps

Same as Test

• 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 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.js 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 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.
• 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

Kapture.2024-12-12.at.10.51.30.mp4

Android: mWeb Chrome

Kapture.2024-12-12.at.10.59.21.mp4

iOS: Native

Kapture.2024-12-12.at.09.18.47.mp4

iOS: mWeb Safari

Kapture.2024-12-12.at.10.10.07.mp4

MacOS: Chrome / Safari

Kapture.2024-12-12.at.08.58.09.mp4

MacOS: Desktop

Kapture.2024-12-12.at.10.30.51.mp4

[melvin-bot]

@allgandalf Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[allgandalf]

Started the review, this is gonna take some time, I will post a feedback today

[allgandalf]

@wildan-m just to be sure, this PR didn't change any functionality right ? we just updated the report action page to be a component.

@luacmartins do you agree with the new name or should we change it to a different name?

[wildan-m]

@allgandalf yes, the functionality change for chatlistitem will be in the 2nd pr

[luacmartins]

Left a few comments of places that are still directly connected to Onyx and make the component not pure

[allgandalf]

Almost done testing, I will finish the checklist today

[luacmartins]

@wildan-m we have conflicts now

[luacmartins]

@allgandalf let's prioritize reviewing this one so we can move on to part 2

[wildan-m]

@luacmartins @allgandalf the conflict has been resolved

[allgandalf]

@allgandalf let's prioritize reviewing this one so we can move on to part 2

Yes, testing it carefully as this affects one of our major component

[allgandalf]

@wildan-m thanks for the changes, they look great!, can you please add videos for all platforms ? just playing around with commenting / adding attachment approving report etc should be fine, we just want to make sure we didn't break anything

[wildan-m]

@allgandalf Sure. The PR has been updated with a random test related to the report action item. I believe it functions the same way as it does in staging.

[allgandalf]

LGTM!, thanks a lot for all the work @wildan-m !!, Let's hope to get this one merged and work on v2 🚀

Also @wildan-m can you please update the testing steps to something more specific like: commenting, sending expenses, creating tasks etc!

[wildan-m]

@allgandalf I think providing detailed test steps for this PR would be excessive, so I will simply update the general activities.

No specific test required, just ensure that the report action item functions correctly as usual.
Ensure these actions works as usual:

• commenting
• sending expenses,
• creating tasks
• add emoji
• reply thread
• mark as unread
• deleting comment

[luacmartins]

@wildan-m we have conflicts again 😞

[wildan-m]

@allgandalf @luacmartins the conflict has been resolved

[luacmartins]

LGTM

[luacmartins]

Great job here!

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.