Keep "Only visible to" tag on all whispers even if there are pending actions #43198

dangrous · 2024-06-06T16:39:07Z

Details

This was introduced in #40020 (comment). As far as I can tell, this shouldn't cause any weirdness elsewhere. I can't think of a situation in which we wouldn't want this to display, even if it WAS a pending whisper. But if you can, let me know!

Fixed Issues

$ #42557

Tests

Same as QA, and also testing the steps from #40020, copied below:
Prerequisites:

Extract transaction id from one of the ReportPreview components
Mock pending transaction using code below

Onyx.merge('cardList', {
        4: {
            bank: 'Expensify Card',
            lastFourPAN: 3458,
        },
    });
    Onyx.merge('transactions_6788826100220673669', {
        amount: 1000,
        currency: 'USD',
        cardID: 4,
        modifiedMerchant: null,
        merchant: 'Test ECard Transaction',
        mccGroup: 'Airlines',
        hasEReceipt: true,
        receipt: {},
        reimbursable: false,
        status: 'Pending',
    });

Check the preview component visible on the highest level of the report
Press the preview and enter the transaction details. Check the header attachment and the preview text.
Create a receipt scan and go through steps 1 and 2 for that type of action while the receipt is being processed.

Verify that no errors appear in the JS console

Offline tests

QA Steps

Create a workspace
Invite another account to that workspace
From the invited account, go to workspace chat
Right click on the welcome whisper message
Click Flag as offensive
Select Spam
Ensure "Only visible to you" is always visible

Additional test:

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Uploading android.mp4…

Android: mWeb Chrome

android-web.mp4

iOS: Native

ios.mp4

iOS: mWeb Safari

ios-web.mp4

MacOS: Chrome / Safari

web-desktop.mp4

MacOS: Desktop

desktop.mp4

melvin-bot · 2024-06-11T18:51:49Z

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

ikevin127 · 2024-06-11T19:39:40Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- 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
- 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 verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
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
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
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.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

android.webm

Android: mWeb Chrome

android-web.webm

iOS: Native

ios.mp4

iOS: mWeb Safari

ios-mweb.mp4

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

ikevin127

🚀 LGTM and tests well for #40020 testing steps too!

melvin-bot · 2024-06-11T20:53:34Z

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

OSBotify · 2024-06-12T11:14:14Z

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

OSBotify · 2024-06-14T23:03:43Z

🚀 Deployed to production by https://github.com/mountiny in version: 1.4.83-3 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

remove check for pending actions

3bfc8c0

dangrous self-assigned this Jun 6, 2024

dangrous marked this pull request as ready for review June 11, 2024 18:51

dangrous requested a review from a team as a code owner June 11, 2024 18:51

melvin-bot bot requested review from ikevin127 and removed request for a team June 11, 2024 18:51

ikevin127 approved these changes Jun 11, 2024

View reviewed changes

melvin-bot bot requested a review from MariaHCD June 11, 2024 20:53

MariaHCD approved these changes Jun 12, 2024

View reviewed changes

MariaHCD merged commit f8e968f into main Jun 12, 2024
18 of 20 checks passed

MariaHCD deleted the dangrous-flaggedwhispertag branch June 12, 2024 11:06

github-actions bot mentioned this pull request Jun 13, 2024

Deploy Checklist: New Expensify 2024-06-13 #43655

Closed

64 tasks

ikevin127 mentioned this pull request Jun 15, 2024

[HOLD for Payment 2024-06-21] Flag message - "Only visible to you" disappears after flagging the whisper, and then reappears #42557

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Keep "Only visible to" tag on all whispers even if there are pending actions #43198

Keep "Only visible to" tag on all whispers even if there are pending actions #43198

dangrous commented Jun 6, 2024 •

edited

Loading

melvin-bot bot commented Jun 11, 2024

ikevin127 commented Jun 11, 2024 •

edited

Loading

ikevin127 left a comment

melvin-bot bot commented Jun 11, 2024

OSBotify commented Jun 12, 2024

OSBotify commented Jun 14, 2024

Keep "Only visible to" tag on all whispers even if there are pending actions #43198

Keep "Only visible to" tag on all whispers even if there are pending actions #43198

Conversation

dangrous commented Jun 6, 2024 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jun 11, 2024

ikevin127 commented Jun 11, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

ikevin127 left a comment

Choose a reason for hiding this comment

melvin-bot bot commented Jun 11, 2024

OSBotify commented Jun 12, 2024

OSBotify commented Jun 14, 2024

dangrous commented Jun 6, 2024 •

edited

Loading

ikevin127 commented Jun 11, 2024 •

edited

Loading