-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-01-16] [$500] Web - IOUs - location text does not change on selecting 'Use current location' #33016
Comments
Triggered auto assignment to @stephanieelliott ( |
Job added to Upwork: https://www.upwork.com/jobs/~0168cfb95cbebc1039 |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - IOUs - location text does not change on selecting 'Use current location' What is the root cause of that problem?We don't pass name param App/src/components/AddressSearch/index.js Lines 338 to 342 in 3df907c
As a result we pass undefined value inside
As a result, the previous value is used What changes do you think we should make in order to solve the problem?In order to fix this, we can use the implementation from WaypointEditor we can set
Plus here(optional)
Like here App/src/pages/iou/WaypointEditor.js Line 167 in 3df907c
What alternative solutions did you explore? (Optional)As alternative, we can pass name param (CONST.YOUR_LOCATION_TEXT or null ) or set name === null by default in
App/src/components/AddressSearch/index.js Lines 338 to 342 in 3df907c
|
ProposalPlease re-state the problem that we are trying to solve in this issue.App displays older location value instead of 'Your location' on selecting 'Use current location' in any waypoint if location access is enabled after error is triggered What is the root cause of that problem?we don't pass the name field to the location here. App/src/components/AddressSearch/index.js Lines 338 to 342 in b950c1e
So that the What changes do you think we should make in order to solve the problem?In here App/src/libs/actions/Transaction.ts Line 61 in b950c1e
We can combine the old transaction and the new change, then use SET method instead of MERGE method as we did here #30290 (comment) Note that: MERGE method caused many similar bugs so we usually use SET method when updating waypoints like here App/src/libs/actions/Transaction.ts Line 162 in b950c1e
What alternative solutions did you explore? (Optional)If we still use MERGE method, I think we should have a general solution instead of fixing case by case (It is so easy to miss similar bugs elsewhere) App/src/libs/actions/Transaction.ts Line 61 in b950c1e
In here we can check if the name field is undefined we will set it to null or address field |
Please re-state the problem that we are trying to solve in this issue.Web - IOUs - location text does not change on selecting 'Use current location' What is the root cause of that problem?When we select use current location name field value show as undefined in
What changes do you think we should make in order to solve the problem?https://github.com/Expensify/App/blob/main/src/pages/iou/request/step/IOURequestStepWaypoint.js#L169 Implement more robust handling of undefined values for name in the
This code explicitly checks for undefined values and assigns Video:-https://drive.google.com/file/d/1gl9HvRNJUpybpImBi6ey1z4u-ktt-tNd/view?usp=sharing |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - IOUs - location text does not change on selecting 'Use current location' What is the root cause of that problem?We use 'Onyx.merge()' to update the 'waypoint' object, but the 'Onyx.merge()' will ignore the property with 'undefined' value, so in this case, all properties in 'waypoint' will be updated except the 'name' property. What changes do you think we should make in order to solve the problem?In here App/src/libs/actions/Transaction.ts Line 60 in b950c1e
We should set the name of the current location to an empty string. What alternative solutions did you explore? (Optional)No ResultBefore.movAfter.mov |
Hey @mananjadhav can you review the proposals please? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
I’ll reproduce the issue and review the proposals by tomorrow. |
@mananjadhav, @stephanieelliott Eep! 4 days overdue now. Issues have feelings too... |
@mananjadhav @stephanieelliott this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
I'll review the proposals by tomorrow. Was out of office earlier and now finishing up priority PRs. |
I don't think we should be using We can work out in the PR places where 🎀 👀 🎀 C+ reviewed. |
Triggered auto assignment to @mountiny, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@mananjadhav, @stephanieelliott, @mountiny, @ZhenjaHorbach Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
1 similar comment
@mananjadhav, @stephanieelliott, @mountiny, @ZhenjaHorbach Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Pr is in review |
@mananjadhav @stephanieelliott @mountiny @ZhenjaHorbach this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ and will need to go internal. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
Adjusting labels to reflect the PR being in review, seems they didn't update automatically like they were supposed to |
PR is on staging |
This was deployed to production on January 9, updating title and labels to reflect 7 day hold |
I couldn't pinpoint the specific PR that must've caused this. I also don't think we need a regression test for this. @stephanieelliott This is ready for payout, can you please post a payment summary? |
Summarizing payment on this issue:
Upwork job is here: https://www.upwork.com/jobs/~1737876297360310272" |
@stephanieelliott When should I expect payment? |
@kaushiktd Payment regarding? |
Yes @mananjadhav |
$500 payment approved to @mananjadhav based on this comment. |
@JmillsExpensify any update on my payment? |
@kaushiktd can you clarify what specifically you are expecting payment for? No payment is due on this issue as your proposal was not selected and you were not hired for this job. For more context into how and when Expensify issues payment please see contributing.md |
It seems I made a mistake. Sorry! I misunderstood this issue for the one I got selected. 😅 |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: v1.4.12-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation: @
Action Performed:
Expected Result:
App should display 'Your location' on selecting 'Use current location' in any waypoint
Actual Result:
App displays older location value instead of 'Your location' on selecting 'Use current location' in any waypoint if location access is enabled after error is triggered
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6312011_1702489356189.windows_chrome_-_your_location_not_displayed.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @stephanieelliottThe text was updated successfully, but these errors were encountered: