Fix: update options when creating task by TMisiukiewicz · Pull Request #39811 · Expensify/App

TMisiukiewicz · 2024-04-08T11:42:41Z

Details

If the task was created, it did not appear on the search list. There was no mechanism responsible for creating new option and putting it in the option list for newly created reports. This solution should be performant, since it looks for the report key that did not exist in the past, creates a single option and updates the report options.

Fixed Issues

$ #39705
PROPOSAL:

Tests

Open a report
Open a report menu and select "Assign task"
Enter the task name and go to the next step
Press "Assignee"
Select other user account from the list
Create a task
Go to the home screen
Go to search
Verify a task with a name provided in the step 3. is visible on the list

Verify that no errors appear in the JS console

Offline tests

n/a

QA Steps

Open a report
Open a report menu and select "Assign task"
Enter the task name and go to the next step
Press "Assignee"
Select other user account from the list
Create a task
Go to the home screen
Go to search
Verify a task with a name provided in the step 3. is visible on the list

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

ANDROID.mp4

Android: mWeb Chrome

ANDROID.WEB.mov

iOS: Native

IOS.mp4

iOS: mWeb Safari

IOS.WEB.mp4

MacOS: Chrome / Safari

WEB.mov

MacOS: Desktop

DESKTOP.mov

…when-creating-task

melvin-bot · 2024-04-09T12:53:50Z

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

mountiny · 2024-04-09T14:35:45Z

@thesahindia 👋 what is your ETA for this pr please? thanks!

thesahindia · 2024-04-09T21:02:33Z

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

Screen.Recording.2024-04-10.at.2.08.02.AM.mov

Android: mWeb Chrome

Screen.Recording.2024-04-10.at.1.59.51.AM.mov

iOS: Native

Screen.Recording.2024-04-10.at.2.30.24.AM.mov

iOS: mWeb Safari

Screen.Recording.2024-04-10.at.2.25.32.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-04-10.at.1.55.27.AM.mov

MacOS: Desktop

Screen.Recording.2024-04-10.at.2.15.55.AM.mov

thesahindia

LGTM!

mountiny · 2024-04-10T00:08:43Z

src/components/OptionListContextProvider.tsx

+        const report = reports[missingReportId];
+
+        if (!report) {
+            return;
+        }


isnt this already captured in the condition above?

mountiny · 2024-04-10T00:08:58Z

src/components/OptionListContextProvider.tsx

        // eslint-disable-next-line react-hooks/exhaustive-deps
    }, [reports]);

+    useEffect(() => {


@TMisiukiewicz can you please add some comment here to explain what this is good for?

added comments to each effect for easier understanding 👍

mountiny

One comment but not a blocker

mountiny · 2024-04-10T20:14:11Z

src/components/OptionListContextProvider.tsx

+        const missingReportId = Object.keys(reports).find((key) => prevReports && !(key in prevReports));
+        const report = missingReportId ? reports[missingReportId] : null;
+        if (!missingReportId || !report) {


What if we merge collection of reports so there would be more reports missing in that single update, can that happen? @TMisiukiewicz

@mountiny that's a valid point, however I couldn't find a quick way how could I test it with many reports, are you aware of any way how to do that? Are merge calls batched? If so, I assume there could be more than just a single ID missing. I can create a follow-up PR moving from find to filter

OSBotify · 2024-04-10T20:22:05Z

✋ 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-04-18T04:56:50Z

🚀 Deployed to staging by https://github.com/mountiny in version: 1.4.63-0 🚀

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

OSBotify · 2024-04-22T14:57:49Z

🚀 Deployed to production by https://github.com/mountiny in version: 1.4.63-21 🚀

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

TMisiukiewicz added 6 commits April 8, 2024 08:56

Merge branch 'main' into fix/update-options-when-creating-task

7774f34

update options list when new new report is added to the list

ceff19e

extend creating options by config

24b0dec

Merge branch 'main' into fix/update-options-when-creating-task

865bbb1

correctly show task on the search list

8c914f0

Merge remote-tracking branch 'upstream/main' into fix/update-options-…

7227a67

…when-creating-task

TMisiukiewicz marked this pull request as ready for review April 9, 2024 12:53

TMisiukiewicz requested a review from a team as a code owner April 9, 2024 12:53

melvin-bot bot requested review from thesahindia and removed request for a team April 9, 2024 12:53

mountiny assigned TMisiukiewicz Apr 9, 2024

thesahindia approved these changes Apr 9, 2024

View reviewed changes

melvin-bot bot requested a review from mountiny April 9, 2024 21:03

mountiny reviewed Apr 10, 2024

View reviewed changes

TMisiukiewicz added 2 commits April 10, 2024 08:34

Merge branch 'main' into fix/update-options-when-creating-task

dd5ecde

update options context and add comments to effects

143b1a4

mountiny approved these changes Apr 10, 2024

View reviewed changes

mountiny merged commit 536f71a into Expensify:main Apr 10, 2024

github-actions bot mentioned this pull request Apr 18, 2024

Deploy Checklist: New Expensify 2024-04-18 #40392

Closed

c3024 mentioned this pull request May 7, 2024

[HOLD for payment 2024-05-06] [HOLD for payment 2024-05-03] CRITICAL: [Actionable Whispers] [$500] Workspace list doesn't show up after creating a workspace for categorize it #40406

Closed

6 tasks

TMisiukiewicz mentioned this pull request May 20, 2024

Search - Created task not displayed in search results until page refreshed #39705

Closed

6 tasks

Conversation

TMisiukiewicz commented Apr 8, 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 9, 2024

Uh oh!

mountiny commented Apr 9, 2024

Uh oh!

thesahindia commented Apr 9, 2024

Reviewer Checklist

Screenshots/Videos

Uh oh!

thesahindia left a comment

Choose a reason for hiding this comment

Uh oh!

mountiny Apr 10, 2024

Choose a reason for hiding this comment

Uh oh!

mountiny Apr 10, 2024

Choose a reason for hiding this comment

Uh oh!

TMisiukiewicz Apr 10, 2024

Choose a reason for hiding this comment

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

mountiny Apr 10, 2024

Choose a reason for hiding this comment

Uh oh!

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

Uh oh!

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Apr 10, 2024

Uh oh!

OSBotify commented Apr 18, 2024

Uh oh!

OSBotify commented Apr 22, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

TMisiukiewicz commented Apr 8, 2024 •

edited

Loading

TMisiukiewicz Apr 11, 2024 •

edited

Loading