Stop sending <mention-report> when not in a policy room #40685

war-in · 2024-04-22T11:45:38Z

Details

Fixed Issues

$ #40480
PROPOSAL:

Tests

Go to some workspace room
Create a comment mentioning another room in the workspace (e. g. #admins)
Verify in the console that the payload of the AddComment request has a <mention-report> tag in the reportComment field
Go to a private chat
Create a comment mentioning a room
Verify in the console that the payload of the AddComment request does not have a <mention-report> tag in the reportComment field

Offline tests

QA Steps

Go to some workspace room
Create a comment mentioning another room in the workspace (e. g. #admins)
Verify in the console that the payload of the AddComment request has a <mention-report> tag in the reportComment field
Go to a private chat
Create a comment mentioning a room
Verify in the console that the payload of the AddComment request does not have a <mention-report> tag in the reportComment field

PR Author Checklist

Screenshots/Videos

Android: Native

Android.Native.mov

Android: mWeb Chrome

android.-.web.mov

iOS: Native

ios.-.native.mov

iOS: mWeb Safari

ios.-.web.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

…t-tag

melvin-bot · 2024-04-23T12:53:59Z

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

ahmedGaber93 · 2024-04-23T19:58:57Z

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

android1.mov

Screen.Recording.2024-04-24.at.1.12.33.PM.mov

Android: mWeb Chrome

android.web1.mov

android.web2.mov

iOS: Native

Screen.Recording.2024-04-24.at.1.57.33.AM.mov

iOS: mWeb Safari

ios.-web1.mov

ios-web2.mov

MacOS: Chrome / Safari

Screen.Recording.2024-04-24.at.1.07.20.AM.mov

MacOS: Desktop

desktop1.mov

desktop2.mov

src/libs/ReportUtils.ts

ahmedGaber93 · 2024-04-23T22:52:25Z

Shouldn't we also edit getCommentLength in useHandleExceedMaxCommentLength and its usage?

App/src/hooks/useHandleExceedMaxCommentLength.ts

Line 11 in f619194

if (ReportUtils.getCommentLength(value) <= CONST.MAX_COMMENT_LENGTH) {

…t-tag

ahmedGaber93

LGTM!

rlinoz

Looks good, just want to discuss parsing the room description

src/libs/ReportUtils.ts

…t-tag # Conflicts: # src/libs/ReportUtils.ts

…t-tag

rlinoz

LGTM!

OSBotify · 2024-05-01T03:01:52Z

🚀 Deployed to staging by https://github.com/rlinoz in version: 1.4.69-0 🚀

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

OSBotify · 2024-05-02T13:05:27Z

🚀 Deployed to production by https://github.com/Beamanator in version: 1.4.69-2 🚀

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

war-in added 5 commits April 22, 2024 13:06

mvp

9da12c4

update getCommentLength

9db4296

update expensify-common

ff600c7

introduce ParsingDetails object

3af8428

Merge branch 'refs/heads/main' into war-in/stop-sending-mention-repor…

909f4c2

…t-tag

robertKozik approved these changes Apr 23, 2024

View reviewed changes

war-in marked this pull request as ready for review April 23, 2024 12:53

war-in requested a review from a team as a code owner April 23, 2024 12:53

melvin-bot bot removed the request for review from a team April 23, 2024 12:53

melvin-bot bot requested a review from ahmedGaber93 April 23, 2024 12:53

ahmedGaber93 reviewed Apr 23, 2024

View reviewed changes

src/libs/ReportUtils.ts Outdated Show resolved Hide resolved

src/libs/ReportUtils.ts Outdated Show resolved Hide resolved

war-in added 2 commits April 26, 2024 09:34

Merge branch 'refs/heads/main' into war-in/stop-sending-mention-repor…

c755b0c

…t-tag

review suggestions

84a54db

war-in requested a review from ahmedGaber93 April 26, 2024 08:03

ahmedGaber93 approved these changes Apr 26, 2024

View reviewed changes

melvin-bot bot requested a review from rlinoz April 26, 2024 15:27

rlinoz reviewed Apr 26, 2024

View reviewed changes

src/libs/ReportUtils.ts Outdated Show resolved Hide resolved

war-in added 3 commits April 30, 2024 10:34

Merge branch 'refs/heads/main' into war-in/stop-sending-mention-repor…

09ef176

…t-tag # Conflicts: # src/libs/ReportUtils.ts

remove sending <mention-report> from room/workspace descriptions

9114d95

Merge branch 'refs/heads/main' into war-in/stop-sending-mention-repor…

e332742

…t-tag

rlinoz approved these changes Apr 30, 2024

View reviewed changes

rlinoz merged commit 095a5c2 into Expensify:main Apr 30, 2024

github-actions bot mentioned this pull request May 1, 2024

Deploy Checklist: New Expensify 2024-05-01 #41376

Closed

59 tasks

melvin-bot bot mentioned this pull request May 2, 2024

[HOLD for payment 2024-05-09] Stop sending <mention-report> when not in a policy room #40480

Closed

allgandalf mentioned this pull request May 27, 2024

[$250] Room - # room from room description is highlighted when edit description #42678

Closed

6 tasks

war-in deleted the war-in/stop-sending-mention-report-tag branch June 24, 2024 09:49

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Stop sending <mention-report> when not in a policy room #40685

Stop sending <mention-report> when not in a policy room #40685

Uh oh!

war-in commented Apr 22, 2024 •

edited

Loading

Uh oh!

melvin-bot bot commented Apr 23, 2024

Uh oh!

ahmedGaber93 commented Apr 23, 2024 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

ahmedGaber93 commented Apr 23, 2024

Uh oh!

ahmedGaber93 left a comment

Uh oh!

rlinoz left a comment

Uh oh!

Uh oh!

rlinoz left a comment

Uh oh!

OSBotify commented May 1, 2024

Uh oh!

OSBotify commented May 2, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Stop sending <mention-report> when not in a policy room #40685

Stop sending <mention-report> when not in a policy room #40685

Uh oh!

Conversation

war-in commented Apr 22, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Apr 23, 2024

Uh oh!

ahmedGaber93 commented Apr 23, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

Uh oh!

Uh oh!

ahmedGaber93 commented Apr 23, 2024

Uh oh!

ahmedGaber93 left a comment

Choose a reason for hiding this comment

Uh oh!

rlinoz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

rlinoz left a comment

Choose a reason for hiding this comment

Uh oh!

OSBotify commented May 1, 2024

Uh oh!

OSBotify commented May 2, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

war-in commented Apr 22, 2024 •

edited

Loading

ahmedGaber93 commented Apr 23, 2024 •

edited

Loading