Allow optimistic assignee chat reports

[thienlnam]

… assignee
cc @jasperhuangg

Details

Fixed Issues

$ #24546
$ https://github.com/Expensify/Expensify/issues/294203
PROPOSAL:

Tests

1. Create a task
2. Assign someone you have not talked to before (but is still a valid account)
3. Verify it creates successfully
4. Verify the chat report between you and the assignee is also created successfully and has the correct message in the LHN
5. Edit the assignee and choose someone you have not chatted with before. Verify that another chat report is created between you and the assignee

• Verify that no errors appear in the JS console

Offline tests

Same as online tests

QA Steps

1. Create a task

2. Assign someone you have not talked to before (but is still a valid account)

3. Verify it creates successfully

4. Verify the chat report between you and the assignee is also created successfully and has the correct message in the LHN

5. Create a task

6. Choose to share in that same chat report, but choose a different assignee that you haven't chatted with before

7. Verify that all the reports are created successfully
   The task report
   The chat report between you and the assignee
   And the share somewhere report is updated correctly

• 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 / Chrome
  • iOS / native
  • iOS / 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 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
    • 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
  • 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 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
  • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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(themeColors.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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Screen.Recording.2023-07-26.at.5.22.14.PM.mov

Mobile Web - Chrome

Screen.Recording.2023-07-26.at.5.23.11.PM.mov

Mobile Web - Safari

Screen.Recording.2023-07-26.at.5.34.17.PM.mov

Desktop

Screen.Recording.2023-07-26.at.5.36.44.PM.mov

iOS

Android

[thienlnam]

Been testing some changes and realized some additional BE changes are required https://github.com/Expensify/Web-Expensify/pull/38300

[thienlnam]

I haven't been able to reproduce the console error after merging main on iOS or mWeb but I'm not sure since my android emulator isn't working.

Also, it's fine to not worry about a failed task right now

[Santhosh-Sellavel]

This occurs on the main too, so its not blocking this.

[Santhosh-Sellavel]

LGTM, thanks!

[melvin-bot]

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

[thienlnam]

Wooo!! Cc @jasperhuangg we're ready to go here

[jasperhuangg]

nicely done! tests well and don't have any qualms with the code

[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.

[ayazhussain79]

@thienlnam @jasperhuangg Unable to select "Assignee" after creating task due to console warning on IOS
https://expensify.slack.com/archives/C049HHMV9SM/p1691795662145199

[thienlnam]

Hmm yeah, apparently when first created the passed report is empty so it doesn't work
But if you exit and go back to the task you can re-assign it fine

[OSBotify]

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.54-0 🚀

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

[OSBotify]

🚀 Deployed to staging by https://github.com/thienlnam in version: 1.3.54-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.3.54-13 🚀

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

[michaelhaxhiu]

👋 is the bug report #25956 a regression from this PR? Curious if we should fix it separately (on the GH linked above) or re-open the parent GH/PR here that this PR touched?

[Santhosh-Sellavel]

I guess follow-up would be the case, cc: @thienlnam can help here!

[thienlnam]

Since the reported bug was over a week from when this PR was deployed, let's go ahead and handle it separately in that issue

[abdulrahuman5196]

pendingFields wasn't added which caused the below bug in offline usecases - #25956

[hungvu193]

This line introduces a bug here where the user chose a brand new assignee (whom they've never chatted with before), and then chose another old assignee, leading to the incorrect merging of isOptimisticReport into the old assignee's account.