Pass ownerLogin as param to isViolationDismissed

[bernhardoj]

Explanation of Change

Fixed Issues

$ #66391
PROPOSAL:

Tests

Same as QA Steps

• Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Prerequisite: have a workspace, user B as the workspace member, user A as the owner and approver

1. [User B] Create 2 reports with duplicates
2. [User A & B] Verify the duplicate violation, next step, and Review duplicates are shown on both reports
3. [User B] Resolve the duplicate on the 1st report
4. [User A & B] Verify the duplicate violation, next step, and Review duplicates disappear
5. [User B] Submit the 2nd report
6. [User A] Approves the report
7. [User A & B] Verify the duplicate violation, next step, and Review duplicates disappear

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

w.2.mp4

w.mp4

[melvin-bot]

@shubham1206agra 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]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7b0cc12a1f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[shubham1206agra]

@bernhardoj Can you add depency array in useOnyx hooks usage?

[bernhardoj]

We don't need the deps array based on this

[codecov]

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
...eaderActions/MoneyReportHeaderSecondaryActions.tsx	0.69% <ø> (ø)
...Item/MoneyRequestReportPreview/PayActionButton.tsx	91.42% <100.00%> (+0.12%)	⬆️
src/components/SettlementButton/index.tsx	82.12% <100.00%> (+0.06%)	⬆️
src/hooks/useLifecycleActions.tsx	57.97% <ø> (ø)
src/hooks/useSearchBulkActions.ts	53.62% <ø> (ø)
src/hooks/useSelectionModePayment.ts	62.13% <100.00%> (+0.37%)	⬆️
src/hooks/useTransactionViolations.ts	100.00% <100.00%> (ø)
src/libs/PaymentUtils.ts	81.73% <ø> (ø)
src/libs/ReportPrimaryActionUtils.ts	93.07% <100.00%> (ø)
src/libs/ReportSecondaryActionUtils.ts	94.67% <100.00%> (ø)
... and 16 more
... and 10 files with indirect coverage changes

[shubham1206agra]

We don't need the deps array based on this

@bernhardoj It's not that simple. The codebase is not ready for this right now. And you have to manually add them for now

[bernhardoj]

Start with removing the dependencies in batches from the App and ultimately remove the argument from onyx.
I think we could take it in reverse - remove the deps carefully from the app first, add a rule so no new useOnyx with deps are added and then once clear, strip it from onyx

Hmm, the plan stated that we start by removing the dependencies first, then remove the argument from Onyx. Is there anything I'm missing?

cc: @fabioh8010 @mountiny

[mountiny]

Hmm, the plan stated that we start by removing the dependencies first, then remove the argument from Onyx. Is there anything I'm missing?

Yeah that is the plan