feat: [Auth Violations] Support isDismissed on newDot to hide violations.

[Krishna2323]

Explanation of Change

Fixed Issues

$ #53398
PROPOSAL: #53398 (comment)

Tests

1. Scan a receipt in which the smartscan will fail (illegible or not a receipt)
2. Go to old Expensify, find the report and dismiss the violation.
3. Go back to new Expensify and make sure the violation is not showing anymore.
4. Note: You might need to refresh the page, I am not sure if the BE is queueing these updates, let me know if not.
5. Create 2 manual expenses with same amount and merchant > Open the first one
6. Go to old Expensify, find the report and dismiss the duplicate violation.
7. Go back to new Expensify and make sure the duplicate violation is not showing anymore.

• Verify that no errors appear in the JS console

Offline tests

1. Scan a receipt in which the smartscan will fail (illegible or not a receipt)
2. Go to old Expensify, find the report and dismiss the violation.
3. Go back to new Expensify and make sure the violation is not showing anymore.
4. Note: You might need to refresh the page, I am not sure if the BE is queueing these updates, let me know if not.
5. Create 2 manual expenses with same amount and merchant > Open the first one
6. Go to old Expensify, find the report and dismiss the duplicate violation.
7. Go back to new Expensify and make sure the duplicate violation is not showing anymore.

QA Steps

1. Scan a receipt in which the smartscan will fail (illegible or not a receipt)
2. Go to old Expensify, find the report and dismiss the violation.
3. Go back to new Expensify and make sure the violation is not showing anymore.
4. Note: You might need to refresh the page, I am not sure if the BE is queueing these updates, let me know if not.
5. Create 2 manual expenses with same amount and merchant > Open the first one
6. Go to old Expensify, find the report and dismiss the duplicate violation.
7. Go back to new Expensify and make sure the duplicate violation is not showing anymore.

• 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 verified the translation was requested/reviewed 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

android_native.mp4

Android: mWeb Chrome

android_chrome.mp4

iOS: Native

ios_native.mp4

iOS: mWeb Safari

ios_safari.mp4

MacOS: Chrome / Safari

web_chrome.mp4

MacOS: Desktop

desktop_app.mp4

[melvin-bot]

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

[Krishna2323]

Hmm, not sure why lint warnings increases every time I commit changes.

[Krishna2323]

@rojiphil, could you please check the ESLint failures below? I have already resolved dozens of those but it keeps increasing everytime I push a commit. I want your help especially in resolving the warning just below this comment and when we use ?? while getting a route, I have no idea how to deal with that, please let me know if you are familiar with that. Thanks 🙏🏻

[rojiphil]

In the case of calling route, can we not do an early return as shown below? It does not seem correct to call navigate with an invalid report id anyway.

The guidelines for the fix of the ESlint failures is already mentioned here. Please look for similar handling for ESlint failures elsewhere in code as that can help. But let me know if you get stuck otherwise.

if(!reportID) {
  return;
}

[Krishna2323]

@rojiphil thanks for the help 🙇🏻.

[Krishna2323]

I will fix ESLint issues again today.

[Krishna2323]

Finally🥴, all the lint issues are fixed, I'm on my way to record the videos... @rojiphil do you know how to replicate RTER violation?

[pecanoro]

@Krishna2323 Is it ready for @rojiphil's review?

[Krishna2323]

@pecanoro, the code changes are done (new ESLint check issues😬). I was trying to record videos for native platforms, and it was failing on iOS a few days back. I will try again and upload them today. By the way, do you know how to replicate an RTER violation?

[pecanoro]

@Krishna2323 This issue is for a different bug but it explains how the RTER violation is triggered: #47511

[Krishna2323]

@pecanoro, I think a company card is required to trigger an RTER violation, or is there alternative way?

[rojiphil]

I think a company card is required to trigger an RTER violation, or is there alternative way?

@Krishna2323 You can record for the remaining scenarios and during PR review stage we can see how we can ensure validating the fix for RTER violation. Does this help?

[pecanoro]

Yeah, we can do that, I will try to find an account that we can use to check if it works for RTER

[Krishna2323]

You can record for the remaining scenarios and during PR review stage we can see how we can ensure validating the fix for RTER violation. Does this help?

Yeah, sure. I will record the videos today. I'm currently busy with a super high-priority PR and have spent many hours resolving the ESLint issues on this PR, but the warnings increase every time I push a commit🤧.

[Krishna2323]

@rojiphil, you can start reviewing this, recordings have been added.

[pecanoro]

@rojiphil Don't forget to get to this when you have some time!