Fix blank map preview on employee side by nkdengineer · Pull Request #51840 · Expensify/App

nkdengineer · 2024-11-01T03:41:44Z

Explanation of Change

Fixed Issues

$ #51285
PROPOSAL: #51285 (comment)

Tests

Precondition:

Admin invited employee to workspace
Distance rates enabled in WS settings & Unit set to Miles in distance rates settings

Employee' side:

Navigate to staging.new.expensify.com
Click >> FAB >> Submit Expense >> Distance tab
Submit distance expense
Go to expense details page

Admin's side:

Go to WS settings >> Distance rates
Select settings option
Change the unit to Kilometer

Employee's side:

On the expense details page, select distance rate field
Select a different rate

Verify that: When admin changes the distance unit setting, map preview for distance expense should update on employee side on selecting distance rate with different unit
However, map preview on admin's side in expense details page gets updated as expected

Verify that no errors appear in the JS console

Offline tests

same as above

QA Steps

same as above

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android.mov

Android: mWeb Chrome

android-mweb.mov

iOS: Native

ios.mov

iOS: mWeb Safari

ios-mweb.mov

MacOS: Chrome / Safari

web-resize.mp4

MacOS: Desktop

web-resize.mp4

melvin-bot · 2024-11-01T07:54:57Z

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

ishpaul777 · 2024-11-04T18:44:16Z

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 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-11-06.at.12.01.21.AM.mov

Android: mWeb Chrome

Screen.Recording.2024-11-06.at.12.03.32.AM.mov

iOS: Native

Screen.Recording.2024-11-05.at.11.47.56.PM.mov

iOS: mWeb Safari

Screen.Recording.2024-11-05.at.11.41.55.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-11-05.at.11.32.43.PM-1.mov

MacOS: Desktop

Screen.Recording.2024-11-06.at.12.49.03.AM.mov

src/libs/Permissions.ts

OSBotify · 2024-11-07T10:26:17Z

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

github-actions · 2024-11-07T13:09:11Z

🚀 Deployed to staging by https://github.com/Gonals in version: 9.0.59-0 🚀

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

paultsimura · 2024-11-08T09:48:37Z

src/libs/actions/IOU.ts

+    if (updatedTransaction?.pendingFields) {
+        pendingFields = {
+            ...pendingFields,
+            ...updatedTransaction?.pendingFields,
+        };
+    }
+


Hey @nkdengineer @ishpaul777, could you please explain this change?

The only place where the pendingFields is used later is here:

App/src/libs/actions/IOU.ts

Lines 2669 to 2678 in 17cae11

optimisticData.push({

onyxMethod: Onyx.METHOD.MERGE,

key: `${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`,

value: {

...updatedTransaction,

pendingFields,

isLoading: hasPendingWaypoints,

errorFields: null,

},

});

Doesn't it do basically the same thing you've introduced here?

@paultsimura The problem is getUpdatedTransaction function can return another pendingFields

Yes, and they will be passed to optimisticData because we use ...updatedTransaction (which includes the new pendingFields) as the first line in the code I've referenced.
Am I missing something?

Yes, and they will be passed to optimisticData because we use ...updatedTransaction (which includes the new pendingFields) as the first line in the code I've referenced.

Yes, that's correct.

Nevermind, I see it now.

github-actions · 2024-11-11T18:14:46Z

🚀 Deployed to production by https://github.com/francoisl in version: 9.0.59-3 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	skipped 🚫
🍎🔄 iOS HybridApp 🍎🔄	skipped 🚫

nkdengineer added 5 commits October 30, 2024 11:56

update getUpdatedTransaction

f9dd9b9

Merge branch 'main' into fix/51285

da13f9e

fix lint

bfd6b16

remove console.log

aa0076a

remove unused type

b4b10a1

nkdengineer marked this pull request as ready for review November 1, 2024 07:54

nkdengineer requested a review from a team as a code owner November 1, 2024 07:54

melvin-bot bot requested a review from ishpaul777 November 1, 2024 07:54

melvin-bot bot removed the request for review from a team November 1, 2024 07:54

Merge branch 'main' into fix/51285

a5227dd

Merge branch 'main' into fix/51285

018b156

ishpaul777 reviewed Nov 5, 2024

View reviewed changes

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

remove useless code

7e9ec7b

ishpaul777 approved these changes Nov 6, 2024

View reviewed changes

melvin-bot bot requested a review from Gonals November 6, 2024 16:53

Gonals approved these changes Nov 7, 2024

View reviewed changes

Gonals merged commit e453cfd into Expensify:main Nov 7, 2024

github-actions bot mentioned this pull request Nov 7, 2024

Deploy Checklist: New Expensify 2024-11-07 #52178

Closed

60 tasks

paultsimura reviewed Nov 8, 2024

View reviewed changes

melvin-bot bot mentioned this pull request Nov 11, 2024

[HOLD for payment 2024-11-18] [$250] Distance - Blank map preview on employee side when selecting distance rate with different unit #51285

Closed

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix blank map preview on employee side#51840

Fix blank map preview on employee side#51840
Gonals merged 8 commits intoExpensify:mainfrom
nkdengineer:fix/51285

nkdengineer commented Nov 1, 2024 •

edited

Loading

Uh oh!

melvin-bot bot commented Nov 1, 2024

Uh oh!

ishpaul777 commented Nov 4, 2024 •

edited

Loading

Uh oh!

Uh oh!

OSBotify commented Nov 7, 2024

Uh oh!

github-actions bot commented Nov 7, 2024

Uh oh!

paultsimura Nov 8, 2024

Uh oh!

nkdengineer Nov 8, 2024

Uh oh!

paultsimura Nov 8, 2024

Uh oh!

nkdengineer Nov 8, 2024

Uh oh!

paultsimura Nov 8, 2024

Uh oh!

github-actions bot commented Nov 11, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

	optimisticData.push({
	onyxMethod: Onyx.METHOD.MERGE,
	key: `${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`,
	value: {
	...updatedTransaction,
	pendingFields,
	isLoading: hasPendingWaypoints,
	errorFields: null,
	},
	});

Conversation

nkdengineer commented Nov 1, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Nov 1, 2024

Uh oh!

ishpaul777 commented Nov 4, 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!

OSBotify commented Nov 7, 2024

Uh oh!

github-actions bot commented Nov 7, 2024

Uh oh!

paultsimura Nov 8, 2024

Choose a reason for hiding this comment

Uh oh!

nkdengineer Nov 8, 2024

Choose a reason for hiding this comment

Uh oh!

paultsimura Nov 8, 2024

Choose a reason for hiding this comment

Uh oh!

nkdengineer Nov 8, 2024

Choose a reason for hiding this comment

Uh oh!

paultsimura Nov 8, 2024

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Nov 11, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

nkdengineer commented Nov 1, 2024 •

edited

Loading

ishpaul777 commented Nov 4, 2024 •

edited

Loading